Red Hat Bugzilla – Bug 1302284
Offline Bricks are starting after probing new node
Last modified: 2016-06-22 01:12:56 EDT
Description of problem:
Have two node cluster with Dis-Rep volume (bricks spread across both the nodes ) and in one of the node glusterd was down and volume status on other running node showed bricks (all) in offline state after glusterd restart. in this state if i peer probe a new node from active running node, the offline bricks will start running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Have two nodes (node-1 and node-2) cluster with Distribute-Replica volume with bricks spread across both the nodes
2.Stop glusterd on node-2
3.Restart glusterd on node-1
4.Check volume status on node-1 //bricks will be in offline state
5.Peer probe node-3 from node-1
6.Check volume status on node-1 //bricks will be running.
Offline bricks are starting after probing new node.
Offline bricks should not start after probing new node.
IMO, this is difficult to fix with having store replicated across all the nodes. However with GlusterD 2.0 this should be doable. I'd like to keep this bug open and track it for 4.0.