[Bugs] [Bug 1555203] New: After a replace brick command, self-heal takes some time to start healing files on disperse volumes

[bugzilla at redhat.com]

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

            Bug ID: 1555203
           Summary: After a replace brick command, self-heal takes some
                    time to start healing files on disperse volumes
           Product: GlusterFS
           Version: 3.10
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org
        Depends On: 1547662
            Blocks: 1555198, 1555201



+++ This bug was initially created as a clone of Bug #1547662 +++

Description of problem:

After a replace brick, self-heal takes some time to start reconstructing the
files, and when it starts, sometimes it pauses for a while.

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


How reproducible:

always

Steps to Reproduce:
1. create a disperse volume
2. replace one brick
3. check new brick contents

Actual results:

New brick is not being filled immediately. It can take some time to start
moving files, and it might make pauses.

Expected results:

Self-heal should trigger immediately after replacing the brick and don't stop
until finished healing all files.

Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1547662
[Bug 1547662] After a replace brick command, self-heal takes some time to
start healing files on disperse volumes
https://bugzilla.redhat.com/show_bug.cgi?id=1555198
[Bug 1555198] After a replace brick command, self-heal takes some time to
start healing files on disperse volumes
https://bugzilla.redhat.com/show_bug.cgi?id=1555201
[Bug 1555201] After a replace brick command, self-heal takes some time to
start healing files on disperse volumes
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.