Hello everybody. I have a problem setting up gluster failover funcionality. Based on manual i setup ucarp which is working well ( tested with ping/ssh etc ) But when i use virtual address for gluster volume mount and i turn off one of nodes machine/gluster will freeze until node is back online. My virtual ip is 3.200 and machine real ip is 3.233 and 3.5. In gluster log i can see: [2011-06-06 02:33:54.230082] I [client-handshake.c:913:client_setvolume_cbk] 0-atlas-client-1: Connected to 192.168.3.233:24009, attached to re mote volume '/atlas'. [2011-06-06 02:33:54.230116] I [afr-common.c:2514:afr_notify] 0-atlas-replicate-0: Subvolume 'atlas-client-1' came back up; going online. [2011-06-06 02:33:54.237541] I [fuse-bridge.c:3316:fuse_graph_setup] 0-fuse: switched to graph 0 [2011-06-06 02:33:54.237801] I [fuse-bridge.c:2897:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 kernel 7.13 [2011-06-06 02:33:54.238757] I [afr-common.c:836:afr_fresh_lookup_cbk] 0-atlas-replicate-0: added root inode [2011-06-06 02:33:54.272650] I [client-handshake.c:913:client_setvolume_cbk] 0-atlas-client-0: Connected to 192.168.3.5:24009, attached to remo te volume '/atlas'. Even when IP i'm using at mount is 3.200 ... Its look like that at the end gluster is using real machine IP's even when i'm connecting to virtual. Is there a way how to turn this functionality off or it is just broken ? thanks for answer Matus
