Re: About Gluster cluster availability when one of out of two nodes is down

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thursday 30 June 2016, Ted Miller <tmiller@xxxxxxxxxxxxxxxxxxx> 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 list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users



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

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux