[Gluster-users] Gluster 3.2.0 and ucarp not working
bxmatus at gmail.com
bxmatus at gmail.com
Mon Jun 6 01:16:16 PDT 2011
thanks for answer. I'm using replications - which is working ok,
volume is mounted using -t glusterfs parameter, does it matter ?
All nodes are using real IP's not virtual ( for probing etc ) , i'm
using virtual only for mounting volume on client. I was waiting over
10 minutes for volume
to "wake up" but it never start to work - it never switch to another
node, even when UCARP was already pointing there, there was lot
of "recovery" messages on log but no attemt to connect to second node.
2011/6/6 Craig Carl <ccarl at gluster.com>:
> Matus -
> Gluster has automatic, built-in failover if you are using replica nodes.
> ucarp is only required if you want highly available NFS mounts.
> To use ucarp with Gluster you should -
> 1. Install Gluster and create a replica volume. 
> 1. DO NOT use the virtual IPs when you peer probe or create
> the volume, that won't work.
> 2. Set the ping-timeout volume option to 25 seconds. 
> 2. Install and setup ucarp.
> 3. Mount your NFS clients using the VIPs.
> 4. Mount your glusterfs clients using the real IP addresses.
> We mostly use CTDB because it supports NFS and Samba, I can't attach a
> document here but I'll email you directly with the documentation.
> Craig Carl, Senior Systems Engineer | Gluster
> 408.829.9953(PST) | http://gluster.com
> On 6/6/11 12:09 AM, bxmatus at gmail.com wrote:
>> 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
>> [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
>> Gluster-users mailing list
>> Gluster-users at gluster.org
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users