A gentle reminder for your feedback, if I don't see any objections on this, the default behaviour is going to change here where daemon processes will be started at the time of glusterd init and irrespective of peer count.
On Thursday 30 June 2016, Atin Mukherjee <amukh...@redhat.com> 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. 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 > -- Atin Sent from iPhone
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
