[Bugs] [Bug 1345727] Bricks are starting when server quorum not met.

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 13 05:18:29 UTC 2016


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



--- Comment #1 from Samikshan Bairagya <sbairagy at redhat.com> ---
+++ This bug was initially created as a clone of Bug #1340995 +++

Description of problem:
=======================
volume bricks are starting when the server quorum not met. 


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-6.


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


Steps to Reproduce:
===================
1. Have three node cluster (n1, n2 and n3)
2. Create a distribute volume using all three node bricks. (3 brick volume )
3. Enable the server side quotum //gluster volume set <vol_name>
cluster.server-quorum-type server
4. stop glusterd in n2 and n3 nodes.
5. Now setup will be in server quorum not met condition //check using volume
status
6. Change the cluster.server-quorum-ratio from default to 95
7. Start glusterd on n2 node
8. Check volume status on n1 and n2 nodes  //you will see the bricks part of n2
node online.

Actual results:
===============
Bricks are starting when server quorum not met.

Expected results:
=================
Bricks should not start when server quorum not met.


Additional info: ( info in /var/log/messages)
=================
On node2:
=========
May 31 00:38:01 dhcp43-216 systemd: Starting GlusterFS, a clustered file-system
server...
May 31 00:38:04 dhcp43-216 etc-glusterfs-glusterd.vol[20626]: [2016-05-31
04:38:04.330963] C [MSGID: 106003]
[glusterd-server-quorum.c:346:glusterd_do_volume_quorum_action] 0-management:
Ser
ver quorum regained for volume Dis. Starting local bricks.
May 31 00:38:04 dhcp43-216 systemd: Started GlusterFS, a clustered file-system
server.

On Node1:
=========
May 31 00:36:01 dhcp43-215 systemd: Starting Session 6710 of user root.
May 31 00:36:54 dhcp43-215 etc-glusterfs-glusterd.vol[12032]: [2016-05-31
04:36:54.296022] C [MSGID: 106002]
[glusterd-server-quorum.c:351:glusterd_do_volume_quorum_action] 0-management:
Ser
ver quorum lost for volume Dis. Stopping local bricks.
May 31 00:37:01 dhcp43-215 systemd: Started Session 6711 of user root.
May 31 00:37:01 dhcp43-215 systemd: Starting Session 6711 of user root.


will provide the console logs


--- Additional comment from Atin Mukherjee on 2016-05-31 02:03:44 EDT ---

This is indeed a bug. Since the volume version has been changed while setting
the server side quorum when N2 comes up it will go for importing the volume
from other nodes. On that code path GlusterD invokes glusterd_start_bricks ()
which never checks for quorum and resulting into starting the bricks.

This doesn't look like a critical issue at this stage. Killing the bricks
processes on N2 and restarting GlusterD should be able to ensure that quorum is
met and bricks are not started. With this explanation moving this bug to 3.2.0

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


More information about the Bugs mailing list