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

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1640581

            Bug ID: 1640581
           Summary: [AFR] : Start crawling indices and healing only if
                    both data bricks are UP in replica 2 (thin-arbiter)
           Product: GlusterFS
           Version: mainline
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: bugs at gluster.org



Description of problem:

Problem: 

Currently in replica 2 volume, if one brick is down and we write/create on
mount point an index entry will be created.
SHD will also keep crawling these index entries even if one brick is down.
That does not makes sense as it can never heal the entry if only one brick is
UP.

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.




Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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