[Bugs] [Bug 1449002] [Brick Multiplexing] : Bricks for multiple volumes going down after glusterd restart and not coming back up after volume start force

[bugzilla at redhat.com]

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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17210 committed in release-3.10 by
Raghavendra Talur (rtalur at redhat.com) 
------
commit 38496dd45780e651647c294b782268557ce31836
Author: Mohit Agrawal <moagrawa at redhat.com>
Date:   Mon May 8 19:29:22 2017 +0530

    glusterd: socketfile & pidfile related fixes for brick multiplexing feature

    Problem: While brick-muliplexing is on after restarting glusterd, CLI is
             not showing pid of all brick processes in all volumes.

    Solution: While brick-mux is on all local brick process communicated
through one
              UNIX socket but as per current code (glusterd_brick_start) it is
trying
              to communicate with separate UNIX socket for each volume which is
populated
              based on brick-name and vol-name.Because of multiplexing design
only one
              UNIX socket is opened so it is throwing poller error and not able
to
              fetch correct status of brick process through cli process.
              To resolve the problem write a new function
glusterd_set_socket_filepath_for_mux
              that will call by glusterd_brick_start to validate about the
existence of socketpath.
              To avoid the continuous EPOLLERR erros in  logs update
socket_connect code.

    Test:     To reproduce the issue followed below steps
              1) Create two distributed volumes(dist1 and dist2)
              2) Set cluster.brick-multiplex is on
              3) kill glusterd
              4) run command gluster v status
              After apply the patch it shows correct pid for all volumes

    > BUG: 1444596
    > Change-Id: I5d10af69dea0d0ca19511f43870f34295a54a4d2
    > Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    > Reviewed-on: https://review.gluster.org/17101
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Prashanth Pai <ppai at redhat.com>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    > (cherry picked from commit 21c7f7baccfaf644805e63682e5a7d2a9864a1e6)

    Change-Id: I1892c80b9ffa93974f20c92d421660bcf93c4cda
    BUG: 1449002
    Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    Reviewed-on: https://review.gluster.org/17210
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Prashanth Pai <ppai at redhat.com>

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