On 06/30/2016 11:40 AM, Atin Mukherjee wrote:
Currently on a two node set up, if node B goes down and node A is
rebooted brick process(es) on node A doesn't come up to avoid split
brains.
This has always been the case. A patch I had sent quite some time back
(http://review.gluster.org/#/c/8034/) was eventually abandoned, I think
`volume start force` should suffice instead of adding checks in code.
-Ravi
However we have had concerns/bugs from different gluster users on the
availability with this configuration. So we can solve this issue by
starting the brick process(es) if quorum is not enabled. If quorum is
enabled we'd not. Although quorum option really doesn't make sense in
a two node cluster, but we can leverage this option to get rid of this
specific situation.
I'd like to know your feedback on this and then I push a patch right away.
~Atin
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
