[Bugs] [Bug 1511301] In distribute volume after glusterd restart, brick goes offline

[bugzilla at redhat.com]

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



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
After glusterd restart on same node, brick goes offline.

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

How reproducible:
3/3

Steps to Reproduce:
1. Created a distribute volume with 3 bricks of each node and start it.
2. Stopped glusterd on other two node and check the volume status where
glusterd is running.
3. Restart glusterd on node where glusterd is running and check volume status.

Actual results:
Before restart glusterd

Status of volume: testvol
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 10.70.37.52:/bricks/brick0/testvol    49160     0          Y       17734

Task Status of Volume testvol
------------------------------------------------------------------------------
There are no active volume tasks

After restart glusterd

Status of volume: testvol
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 10.70.37.52:/bricks/brick0/testvol    N/A       N/A        N       N/A  

Task Status of Volume testvol
------------------------------------------------------------------------------
There are no active volume tasks


Expected results:
Brick must be online after restart glusterd.

Additional info:
Glusterd is stopped on other two nodes.

--- Additional comment from Worker Ant on 2017-11-06 03:02:33 EST ---

REVIEW: https://review.gluster.org/18669 (glusterd: restart the brick if qorum
status is NOT_APPLICABLE_QUORUM) posted (#1) for review on master by Atin
Mukherjee

--- Additional comment from Worker Ant on 2017-11-09 00:11:06 EST ---

COMMIT: https://review.gluster.org/18669 committed in master by  

------------- glusterd: restart the brick if qorum status is
NOT_APPLICABLE_QUORUM

If a volume is not having server quorum enabled and in a trusted storage
pool all the glusterd instances from other peers are down, on restarting
glusterd the brick start trigger doesn't happen resulting into the
brick not coming up.

Change-Id: If1458e03b50a113f1653db553bb2350d11577539
BUG: 1509845
Signed-off-by: Atin Mukherjee <amukherj 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.