[Bugs] [Bug 1305256] New: GlusterD restart, starting the bricks when server quorum not met

[bugzilla at redhat.com]

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

            Bug ID: 1305256
           Summary: GlusterD restart, starting the bricks when server
                    quorum not met
           Product: GlusterFS
           Version: 3.7.7
         Component: glusterd
          Keywords: ZStream
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bsrirama at redhat.com, bugs at gluster.org,
                    sasundar at redhat.com
        Depends On: 1298068, 1298439



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

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

Description of problem:
=======================
Had 5 node cluster (n1, n2, n3, n4 & n5 ) with one distributed volume with
server quorum enabled  and stopped glusterd in 3 nodes (n3,n4 and n5) and
checked the volume status in n1 node, the bricks were offline and restarted the
glusterd on that node (n1) and checked the volume status again, this time it
bricks are in online.

Version-Release number of selected component (if applicable):
==============================================================
glusterfs-3.7.5-15


How reproducible:
=================
Always

Steps to Reproduce:
===================
1. Have 5 node cluster with one distributed volume
2. Enable the server quorum
3. Bring down 3 nodes ( Eg , n3, n4 and n5)
4. Check the volume status in node-1 (n1) // bricks will be in offline state
5. Restart glusterd on node-1
6. Check the volume status // bricks will be in online state

Actual results:
===============
bricks are in online when server quorum not met


Expected results:
=================
Bricks should be in offline state when server quorum not met

--- Additional comment from Vijay Bellur on 2016-01-14 00:52:58 EST ---

REVIEW: http://review.gluster.org/13236 (glusterd: check quorum on restart
bricks) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Vijay Bellur on 2016-01-26 10:02:08 EST ---

REVIEW: http://review.gluster.org/13236 (glusterd: check quorum on restart
bricks) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Vijay Bellur on 2016-02-02 22:29:47 EST ---

REVIEW: http://review.gluster.org/13236 (glusterd: check quorum on restart
bricks) posted (#3) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Vijay Bellur on 2016-02-05 10:26:46 EST ---

COMMIT: http://review.gluster.org/13236 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 2fe4f758f4f32151ef22d644c4de1e58a508fc3e
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Jan 14 11:11:45 2016 +0530

    glusterd: check quorum on restart bricks

    While spawning bricks on a glusterd restart the quorum should be checked
and
    brick shouldn't be started if the volume doesn't meet quorum.

    Change-Id: I21bf9055bdf38c53c81138cc204ba05a9ff6444f
    BUG: 1298439
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/13236
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1298068
[Bug 1298068] GlusterD restart, starting the bricks when server quorum not
met
https://bugzilla.redhat.com/show_bug.cgi?id=1298439
[Bug 1298439] GlusterD restart, starting the bricks when server quorum not
met
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.