[Bugs] [Bug 1297172] New: Client self-heals block the FOP that triggered the heals

[bugzilla at redhat.com]

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

            Bug ID: 1297172
           Summary: Client self-heals block the FOP that triggered the
                    heals
           Product: GlusterFS
           Version: mainline
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
If a lookup or a read transaction FOP triggers an inode refresh, the FOP does
not return until the heal completes. For VM use cases, this could mean the VM
appearing to go to an unresponsive state until the heal completes.

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


How reproducible:
Always

Steps to Reproduce:
1.Create a 1x2 replica, fuse mount and create a file.
2.Disable self-heal daemon
2.Kill a brick, `dd` a few gigs into the file.
3.Bring the brick back up, do a hexdump of file from the mount.
4.Hexdump will stall spewing out data until the data heal completes (as seen
from the mount log)

Actual results:
FOP blocks until heal is done.

Expected results:
FOP should not wait for heals- they could be made to happen in the background.

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