[Bugs] [Bug 1741899] the volume of occupied space in the bricks of gluster volume (3 nodes replica) differs on nodes and the healing does not fix it

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 30 07:37:14 UTC 2019


--- Comment #14 from Krutika Dhananjay <kdhananj at redhat.com> ---
(In reply to Ravishankar N from comment #13)
> Adding the Sharding maintainer Krutika to the bug for any possible advice on
> comment#12.

Copying the shards across bricks from the backend is not a good idea. A
parallel operation on the file while the copy is going on can lead to

Seems like the main issue is replication inconsistency after a replace-brick.
Any heal-related errors in the logs?
I see cluster.favorite-child-policy set in volume-info. Would it be an issue

(As an aside, network.ping-timeout is set to 5s and that's really low. @Sergey,
you should probably set to a higher value, say 30s or more)


You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list