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

2016-07-05 Thread a.hol...@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: "

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

2016-07-02 Thread Atin Mukherjee
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 wrote: >

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

2016-06-30 Thread Atin Mukherjee
On Thursday 30 June 2016, Ted Miller wrote: > Is it not the default behavior that if a volume looses quorum, the files > are still available in read-only mode? If so, it makes sense to me that > this behavior would continue after a reboot. Otherwise the user is

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

2016-06-30 Thread Atin Mukherjee
On Thu, Jun 30, 2016 at 11:57 AM, Ravishankar N wrote: > 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

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

2016-06-30 Thread Ravishankar N
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

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

2016-06-30 Thread Atin Mukherjee
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