-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data stored in a Jiva PVC doesn't replicate #367
Comments
Investigated further and it is actually the Dynamic NFS pod ephemeral storage where the data gets held up without passing it to Jiva at all. |
Reopening this issue because it seems to do with Jiva side after all. Tested with a minimum example with a Jiva replication set up, and the problem happens even without Dynamic NFS Provisioner. It seems to be CSI, OpenEBS or Jiva issue, possibly I have misunderstood something. Applying these resources and then using
This mount also seems to prevent the pod deletion, except using I installed OpenEBS Jiva separately, I now notice that installing OpenEBS separately adds some pods named |
Even with a clean installation of a single node MicroK8S cluster with OpenEBS Jiva installed with Helm to an empty cluster, set with replicationFactor=1, writing a gigabyte file to a PVC mount doesn't actually go to the replica:
No errors, no idea what is going on here. |
Got it working, by installing Jiva with:
I have no clue what the difference is. The hostpath points to Other differences:
|
What steps did you take and what happened:
I am using Dynamic NFS Provisioner on top of triple replicated Jiva volumes to make them ReadWriteMany.
After hard reboots, this seems to always happen:
It seems to me the data stored to the Jiva volumes do not go to the replicas, but instead go to the mounting pod local ephemeral storage.
I would expect the data to go to the replicas which are correctly set up, but instead Jiva stores the files to:
/var/snap/microk8s/common/var/lib/kubelet/pods/4ae2b03c-e03e-4088-92cb-dcf37ae2e118/volumes/kubernetes.io~csi/pvc-4f872aeb-385e-44e0-b0f1-9643a04ea4af/mount
Which doesn't seem to be mounted anywhere.
What did you expect to happen:
I would expect either an error in OpenEBS Jiva pvc pod start-up, or the Jiva replicas to be mounted to the mount directory using CSI/iSCSI so the data ends up on the replicas.
The output of the following commands will help us better understand what's going on:
Environment:
kubectl version
):Using MicroK8S v1.25.5
/etc/os-release
):Ubuntu 22.04.1 LTS
The text was updated successfully, but these errors were encountered: