[Bugs] [Bug 1466608] New: multiple brick processes seen on gluster(fs) d restart in brick multiplexing

[bugzilla at redhat.com]

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

            Bug ID: 1466608
           Summary: multiple brick processes seen on gluster(fs)d restart
                    in brick multiplexing
           Product: Red Hat Gluster Storage
           Version: 3.3
         Component: glusterd
          Keywords: Triaged
          Assignee: amukherj at redhat.com
          Reporter: amukherj at redhat.com
        QA Contact: bmekala at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    storage-qa-internal at redhat.com, vbellur at redhat.com
        Depends On: 1465559



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

Description of problem:

On a brick multiplexing test setup if all the gluster processes are killed and
glusterd is started there is a race window where one of the brick will fail to
attach to one of the running brick instances and while doing so, it will try to
bring up a new process resulting in deleting the socket file which has been
used by one of the other brick processes resulting into brick disconnect too.

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

How reproducible:
Often, not always

--- Additional comment from Worker Ant on 2017-06-27 11:54:26 EDT ---

REVIEW: https://review.gluster.org/17640 (glusterd: mark brickinfo to started
on successful attach) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Worker Ant on 2017-06-27 11:55:46 EDT ---

REVIEW: https://review.gluster.org/17640 (glusterd: mark brickinfo to started
on successful attach) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Worker Ant on 2017-06-28 02:19:05 EDT ---

COMMIT: https://review.gluster.org/17640 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 24d09edf4b13d72a8707c801939921de0d32d4dd
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Tue Jun 27 21:09:49 2017 +0530

    glusterd: mark brickinfo to started on successful attach

    brickinfo's port & status should be filled up only when attach brick is
    successful.

    Change-Id: I68b181be37cb94d176f0f4692e8d9dac5493181c
    BUG: 1465559
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: https://review.gluster.org/17640
    Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan at gmail.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1465559
[Bug 1465559] multiple brick processes seen on gluster(fs)d restart in
brick multiplexing
-- 
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=bW6AtHuA4f&a=cc_unsubscribe