[Gluster-users] About Gluster cluster availability when one of out of two nodes is down

[a.holden at t-online.de]

Please Remove All eMail accounts that are being sent to *.*.holden.de
 
thankyou in advance
 
Andy Holden
 
 
 
 
 
 
 
-----Original-Nachricht-----
Betreff: Re: [Gluster-users] About Gluster cluster availability when one of 
out of two nodes is down
Datum: 2016-07-02T11:44:39+0200
Von: "Atin Mukherjee" <amukherj at redhat.com>
An: "gluster-users at gluster.org" <gluster-users at gluster.org>, 
"gluster-devel at gluster.org" <gluster-devel at gluster.org>
 
 
 
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 <amukherj at redhat.com
<mailto:amukherj at 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


<div style=\"border:0;border-bottom:1px solid black;width:100%;\"> 
Gesendet mit Telekom Mail <https://t-online.de/email-kostenlos> - kostenlos 
und sicher für alle!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160702/a4ac0644/attachment.html>