[Bugs] [Bug 1227656] Glusted dies when adding new brick to a distributed volume and converting to replicated volume

[bugzilla at redhat.com]

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



--- Comment #5 from Kaushal <kaushal at redhat.com> ---
This is a bug with how server quorum has been implemented.

If server quorum is enabled on a volume, a GlusterD will only allow the brick
processes of the volume to run iff it sees a quorum of other GlusterDs. What
this means is that, a GlusterD when starting should not immediately start any
bricks of such a volume.

But as it is currently implemented, GlusterD will not start any bricks,
irrespective of whether server quorum is enabled on any volume or not, if it
sees there are more than 1 peers in the cluster. Immediately after the GlusterD
connects to another GlusterD, the bricks will be started.

This issue has been known for sometime, and is particularly troublesome with 2
node clusters. The suggested current workaround is to have a dummy 3rd node
which doesn't host any bricks, but just runs GlusterD be a part of the cluster.
This node will remain online always, and allow the other GlusterDs to start
bricks quickly when restarting.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=TvjdbXeg4g&a=cc_unsubscribe