A much simpler answer is to assign a hostname to multiple IP addresses
(round robin dns). When gethostbyname() returns multiple entries, the
client will try them all until it's successful.
On 11/24/2014 06:23 PM, Paul Robert Marino wrote:
This is simple and can be handled in many ways.
Some
volume not automounted when peer is down
A much simpler answer is to assign a hostname to multiple IP addresses (round robin dns). When gethostbyname() returns multiple entries, the client will try them all until it's successful.
On 11/24/2014 06:23 PM, Paul Robert Marino wrote:
This is simple
thing, won’t it?
Confused,
Eric
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On Behalf Of Joe Julian
Sent: Tuesday, November 25, 2014 1:04 PM
To: gluster-users@gluster.org
Subject: Re: [Gluster-users] Gluster volume not automounted when peer
Subject: Re: [Gluster-users] Gluster volume not automounted when peer is down
Hmmm. I can see how that would work if you had an external client that wanted
to connect to a cluster, and one of the nodes was down; it would need to pick
another node in the cluster, yes. But that’s not my scenario
Hi all,
We're trying to use gluster as a replicated volume. It works OK when both
peers are up but when one peer is down and the other reboots, the surviving
peer does not automount glusterfs. Furthermore, after the boot sequence is
complete, it can be mounted without issue. It automounts
This is simple and can be handled in many ways.Some background first.The mount point is a single IP or host name. The only thing the client uses it for is to download a describing all the bricks in the cluster. The next thing is it opens connections to all the nodes containing bricks for that
