[Need Help]When I upload a file directly to the server's mount path of kadalu pvc, the file cannot be identified in the corresponding pod. about kadalu HOT 5 OPEN

This is not a use case which is supported by Gluster. Gluster has some internal data which gets added along with the file when created using mountpoint. They will be missing when the file gets added directly.

from kadalu.

This is not a use case which is supported by Gluster. Gluster has some internal data which gets added along with the file when created using mountpoint. They will be missing when the file gets added directly.

Besides Gluster's own support, is this issue related to the type of kadaluStorage? Because in another k8s cluster, I created kadaluStorage using the replica2 and replica3 types, and I directly uploaded files to the mount paths of these two types of servers. They were able to be read normally in the pod.Or, this issue is only caused by the characteristics of Glusterfs when a single node uses Gluster to store files?

from kadalu.

This is not a use case which is supported by Gluster. Gluster has some internal data which gets added along with the file when created using mountpoint. They will be missing when the file gets added directly.

Besides Gluster's own support, is this issue related to the type of kadaluStorage? Because in another k8s cluster, I created kadaluStorage using the replica2 and replica3 types, and I directly uploaded files to the mount paths of these two types of servers. They were able to be read normally in the pod.Or, this issue is only caused by the characteristics of Glusterfs when a single node uses Gluster to store files?

Yes it might be because of type of kadalustorage selected.
Replica1 is equivalent to pure distribute type in glusterfs, and requires the data to be set through client side for it to be placed in a algo based(through dht translator) predictable path to store and retrieve from nodes, which might not be the case with replicas as all data is stored in all nodes.

But anyway as @amarts stated, here storage use case is to store the data from client side and retrieve from server nodes.

from kadalu.

This is not a use case which is supported by Gluster. Gluster has some internal data which gets added along with the file when created using mountpoint. They will be missing when the file gets added directly.

Besides Gluster's own support, is this issue related to the type of kadaluStorage? Because in another k8s cluster, I created kadaluStorage using the replica2 and replica3 types, and I directly uploaded files to the mount paths of these two types of servers. They were able to be read normally in the pod.Or, this issue is only caused by the characteristics of Glusterfs when a single node uses Gluster to store files?

Yes it might be because of type of kadalustorage selected. Replica1 is equivalent to pure distribute type in glusterfs, and requires the data to be set through client side for it to be placed in a algo based(through dht translator) predictable path to store and retrieve from nodes, which might not be the case with replicas as all data is stored in all nodes.

But anyway as @amarts stated, here storage use case is to store the data from client side and retrieve from server nodes.

Okay, thank you very much

from kadalu.

This is not a use case which is supported by Gluster. Gluster has some internal data which gets added along with the file when created using mountpoint. They will be missing when the file gets added directly.

Besides Gluster's own support, is this issue related to the type of kadaluStorage? Because in another k8s cluster, I created kadaluStorage using the replica2 and replica3 types, and I directly uploaded files to the mount paths of these two types of servers. They were able to be read normally in the pod.Or, this issue is only caused by the characteristics of Glusterfs when a single node uses Gluster to store files?

That works because replica2 (or replica3) does a self-heal logic). In case of replica1 (or is called distribute), which doesn't come with any self-heal logic, and hence in that case, the backend writing is not supported.

But in general, its a good practise to never write directly to backend. (think of you updaing a xfs / ext4 block directly while FS is mounted, it would corrupt the system).

from kadalu.