Anand Avati a écrit :
> 2. the protocol/client handles round-robin DNS gracefully. you can have just
> one protocol/client section in the client specification which has a hostname
> which resolves to 3 differnt server IPs (either via bind configuration, or
> multiple /etc/hosts entries for differnt IP and same hostname).
So something like :
volume santa
type protocol/client
option transport-type tcp/client
option remote-host servers.mygluster.lan
option remote-subvolume mailspool
end-volume
Where servers.mygluster.lan resolves either 10.64.98.147, 10.64.98.144,
and 10.64.98.146 (in this example)
> When one server disconnects, glusterfs now automatically tries the
> second IP from the dns reply. (loops over to the next IP per
> reconnection and then does a fresh DNS lookup after one iteration) -
> This option can work as an intermediate solution until the HA xlator
> comes in.
Sebastien.
