[Bugs] [Bug 1647506] New: glusterd_brick_start wrongly discovers already-running brick

[bugzilla at redhat.com]

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

            Bug ID: 1647506
           Summary: glusterd_brick_start wrongly discovers already-running
                    brick
           Product: GlusterFS
           Version: 4.1
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: patrice at buleon.net
                CC: bugs at gluster.org



Description of problem:
After a gluster node restart, a brick process is not started


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


How reproducible:
The gluster node runs in a docker container
We have 2 volumes (vol1 and vol2)
At the first start the bricks process pid are
 - 27 for vol1
 - 28 for vol2
After the restart, the pid files are not removed 
Gluster checks if the brick for vol1 is started, and because there is no
process with pid 27, it starts it. Unfortunately this new process has the pid
28
Then gluster checks if the brick for vol2 is started, and read the old pid file
which contains 28. And unfortunately pid 28 is the pid of the brick of vol1
-> and gluster doesn't start the brick of vol2

Gluster has to check the process found in pid file is really a process for the
good brick (not a process started for a previous brick)


Steps to Reproduce:

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.