[Bugs] [Bug 1302284] New: Offline Bricks are starting after probing new node
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jan 27 11:33:15 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1302284
Bug ID: 1302284
Summary: Offline Bricks are starting after probing new node
Product: GlusterFS
Version: 3.7.5
Component: glusterd
Severity: high
Assignee: bugs at gluster.org
Reporter: bsrirama at redhat.com
CC: bugs at gluster.org
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):
=============================================================
glusterfs-3.7.5-17
How reproducible:
=================
Every time
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.
Actual results:
===============
Offline bricks are starting after probing new node.
Expected results:
=================
Offline bricks should not start after probing new node.
Additional info:
--
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