[Gluster-users] One node goes offline, the other node can't see the replicated volume anymore
GregScott at infrasupport.com
Sat Jul 13 23:58:15 UTC 2013
Log files sent privately to Joe. If others from the community want to look at them, I’m OK with posting them here. I don’t think they have anything confidential. Now that I know about that 42 second timeout, the behavior makes more sense. Why 42? What’s special about 42? Is there a way I adjust that down for my application to, say, 1 or 2 seconds?
From: Joe Julian [mailto:joe at julianfamily.org]
Sent: Saturday, July 13, 2013 4:28 PM
To: Greg Scott; 'gluster-users at gluster.org'
Subject: Re: [Gluster-users] One node goes offline, the other node can't see the replicated volume anymore
Huh.. this was in my sent folder... let's try again.
There's something missing from this picture. The logs show that the client is connecting to both servers, but it only shows the disconnection from one and claims that it's not connected to any bricks after that.
Here's the data I'd like to have you generate:
unmount the clients
gluster volume set firewall-scripts diagnostics.client-log-level DEBUG
gluster volume set firewall-scripts diagnostics.brick-log-level DEBUG
systemctl stop glusterd.service
truncate the client, glusterd, and server logs
systemctl start glusterd
Do your iptables disconnect
telnet $this_host_ip 24007 # report whether or not it establishes a connection
wait 42 seconds
Remove the iptables rule
tar up the logs and email them to me.
You can reset the log-level:
gluster volume reset firewall-scripts diagnostics.client-log-level
gluster volume reset firewall-scripts diagnostics.brick-log-level
lastly, do you have a loopback interface (lo) on 127.0.0.1 and is localhost defined in /etc/hosts?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users