[Bugs] [Bug 1300875] Client self-heals block the FOP that triggered the heals

[bugzilla at redhat.com]

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


--- Doc Text *updated* by Ravishankar N <ravishankar at redhat.com> ---
Previously, if a FOP viz. lookup, read etc. on an AFR sub volume triggered an inode-refresh and a subsequent heal, the FOP would be served only after the self-heal completes. The client that issued the FOP would have to wait until such time. With this fix, the FOP will be served immediately and any self-heal required is queued and will happen in the background. The number of such background self-heals that can happen via the client can be throttled via the 'background-self-heal-count' and 'heal-wait-queue-length' volume options.


-- 
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=HJqddFyyAM&a=cc_unsubscribe