[Bugs] [Bug 1509845] In distribute volume after glusterd restart, brick goes offline
bugzilla at redhat.com
bugzilla at redhat.com
Mon Nov 6 08:01:10 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1509845
--- 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.
--
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