[Bugs] [Bug 1168080] All the bricks on one of the node goes offline and doesn't comes back up when one of the node is shutdown and the other node is rebooted in 2X2 gluster volume.

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |amukherj at redhat.com
         Resolution|---                         |NOTABUG
        Last Closed|                            |2014-11-26 00:46:13



--- Comment #2 from Atin Mukherjee <amukherj at redhat.com> ---
As per the design, brick daemons will not be started until a friend update is
received if there are other peers in the cluster, this is just to ensure that
the node which is coming up doesn't end up with spawning daemons with stale
data. 

In this case, since it was 2 node cluster and one node was down the brick
daemons were not started as the friend update was not received. 

However we can start the brick daemons by an volume start force to bypass this
check.

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