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

[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: "Atin Mukherjee" <amukh...@redhat.com>
An: "gluster-users@gluster.org" <gluster-users@gluster.org>, 
"gluster-de...@gluster.org" <gluster-de...@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 <amukh...@redhat.com
<mailto: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


 
Gesendet mit Telekom Mail <https://t-online.de/email-kostenlos> - kostenlos 
und sicher für alle!___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[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:

> 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-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[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 going
> to be very confused.
>
I must say that I should have mentioned it as server side quorum to avoid
this confusion. In this specific case brick process(es) do not come up
which means volume is completely inaccessible and you don't get to access
the files hosted by the volume.


> Ted Miller
> Elkhart, IN, USA
>
> On 6/30/2016 2:10 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. 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 listgluster-us...@gluster.org 
> http://www.gluster.org/mailman/listinfo/gluster-users
>
>
>

-- 
--Atin
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[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 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.
>

This is exactly what I thought earlier as a workaround. The problem with
this approach here is the manual intervention which users may not like to
apply. I got to know from Joe Julian that this is a departure from prior
behaviour and I got a feedback that we should think about having a solution
where there is no manual intervention/workaround required.


-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 
> listGluster-users@gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-users
>
>
>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[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 
(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
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users



___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[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
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
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users