One node goes offline, the other node can't see the replicated volume anymore

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

 



I was out all day yesterday - is there anything I can do to fix this problem or is this just pretty much how Gluster works?

- Greg


-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Greg Scott
Sent: Thursday, July 11, 2013 6:44 PM
To: 'Joe Julian'
Cc: 'gluster-users at gluster.org'
Subject: Re: One node goes offline, the other node can't see the replicated volume anymore

So back to the problem at hand - I think what's going on is, both nodes fw1 and fw2 try to satisfy reads from fw1 first.  That's why fw2 can't find the /firewall-scripts file system when it becomes isolated from fw1, and why fw1 always seems to be able to find it.  What makes fw1 so important?  Near as I can tell, because fw1 is the first in the list and I used node fw1 to set up my Gluster volume.  

So after putting up with me for page after page of text digging into the problem details, is there anything we can do to tell Gluster to satisfy reads locally, especially when the other brick is offline?  

Thanks

- Greg
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://supercolony.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