[Bugs] [Bug 1640581] [AFR] : Start crawling indices and healing only if both data bricks are UP in replica 2 (thin-arbiter)

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 24 00:56:53 UTC 2018


--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/21448 committed in master by "Ravishankar N"
<ravishankar at redhat.com> with a commit message- cluster/afr : Check for UP
bricks before starting heal

Currently for replica volume, even if only one brick is UP
SHD will keep crawling index entries even if it can not
heal anything.

In thin-arbiter volume which is also a replica 2 volume,
this causes inode lock contention which in turn sends
upcall to all the clients to release notify locks, even
if it can not do anything for healing.

This will slow down the client performance and kills the
purpose of keeping in memory information about bad brick.

Solution: Before starting heal or even crawling, check if
sufficient number of children are UP and available to check
and heal entries.

Change-Id: I011c9da3b37cae275f791affd56b8f1c1ac9255d
updates: bz#1640581
Signed-off-by: Ashish Pandey <aspandey at redhat.com>

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=heGSYSZV7R&a=cc_unsubscribe

More information about the Bugs mailing list