mohammaddawoodshaik

[Bug]: In Replica3 KadaluStorage FUSE is showing subdir as TranportEndpointNotConnected

10

We are using Kadalu(1.1.0) for one of our usecase with KadaluStorage-Replica-3 As part of our highAvailability we have brought down one instance of the brick pod and seeing a issue...

App's FUSE mount goes to `Transport Endpoint not connected`

7

**Describe the bug** By any chance if kadalu-provisioner gets restarted then all the application having GlusterFS mount will start displaying `TransportENdpoint is not connected` even after kadalu-provisioner is came backup....

[Bug]: In Replica 3, one node endup with different GFID for `subvol` directory

1

**Describe the bug** We have 3-node setup of K8s, in which we are deploying KadaluStorage-Replica-3, with each node hosting one brick-server pod and along with nodeplugin pods running in all...

[Bug]: Data is not synced across the FUSE mounts(Kadalu-nodePlugin pods)

1

**Describe the bug** We have 3-node setup of K8s, in which we are deploying KadaluStorage-Replica-3, with each node hosting one brick-server pod and along with nodeplugin pods running in all...

Kadalu-GlusterFS Heal is taking more time/stuck after node remove and addition of new node.

3

In our K8 cluster cluster, we have a KadaluStorage deployed with Replica3. Following is the spec for the same. `apiVersion: kadalu-operator.storage/v1alpha1 kind: KadaluStorage metadata: name: cvol namespace: ns spec: pvReclaimPolicy:...