These pairs could be pinged and/or tested before the Filesystem RA tries = to connect to them. In case that one of these nodes is not reachable or = does not respond to the connection attempt the RA could try a connection = with the next nvpair. Background: I would like to build a openais/pacemaker cluster consisting of three = nodes. On each node should run a gluster server providing a replicated = glusterfs share, a glusterfs client (Filesystem RA clone) connected to this share = and one or more KVM-VMs=20 Due to load reason the VMs should be distributed over the cluster. In = case of crash of one of these servers the affected VM shall fail over to the remaining nodes. I hope I was able to explain my concerns and you or anybody else could = give me a hint to solve my problem. Thx in advance Uwe -----Urspr=FCngliche Nachricht----- Von: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] Im Auftrag von Marcel = Pennewi=DF Gesendet: Montag, 18. Juli 2011 14:00 An: gluster-users at gluster.org Betreff: Re: glusterfs and pacemaker On Monday 18 July 2011 13:26:00 samuel wrote: > I don't know from which version on but, if you use the native client=20 > for mounting the volumes, it's only required to have the IP active in=20 > the mount moment. After that, the native client will transparently=20 > manage node's failure. ACK, that's why we use this shared IP (e.g. for backup issues via nfs). AFAIR glusterFS retrieves Volfile (via shared IP) and connects to the = nodes. Marcel _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
