Red Hat Bugzilla – Bug 763570
handle peer detach gracefully in case of lost frames
Last modified: 2015-12-01 11:45:32 EST
I read your notes, I saw the dropped frames in the logs. These two machines are running as VM's on the same KVM host. There is NO way there are network issues. The VM host has 0 load and is the fastest machine in the building. This patch may fix the problem but I think you are wrong as to root cause.
(In reply to comment #1)
> Pranith -
> I read your notes, I saw the dropped frames in the logs. These two machines
> are running as VM's on the same KVM host. There is NO way there are network
> issues. The VM host has 0 load and is the fastest machine in the building. This
> patch may fix the problem but I think you are wrong as to root cause.
The logs on the box 240, had a lot of error logs about resolving the the ip-address of its peers. There were errors about get_addrinfo () failures.
We tried pinging one machine from the other, that gave problems too. So we came to the conclusion based on the frames lost logs that this is the reason. Let me also talk to some of the folks who implemented the communication interface and get back to you as to why else this may happen.
There are two friends in the cluster. When a detach is initiated from one machine, if the other machine gets the request but its response is lost because of network issues, the second peer detach to the same machine will cause the following crash on the machine that is being detached.
[2010-10-05 22:05:20.202143] I [glusterd-sm.c:707:glusterd_friend_sm_inject_event] glusterd: Enqueuing event: 9
signal received: 6
time of crash: 2010-10-05 22:05:20
package-string: glusterfs 3.1.0qa40
> The logs on the box 240, had a lot of error logs about resolving the the
> ip-address of its peers. There were errors about get_addrinfo () failures.
> We tried pinging one machine from the other, that gave problems too. So we came
> to the conclusion based on the frames lost logs that this is the reason. Let me
Could this be a platform issue? you need to check if the DNS resolver was working fine since we have been seeing issues off-late with that.
If a hostname doesn't gets resolved this will be the general problem with RPC and also NFS.. so forth.
PATCH: http://patches.gluster.com/patch/5421 in master (mgmt/glusterd: handle reqs from unknown peers for friend sm)
This bug is resolved in Glusterd. Since we are not going to actively work on platform we decided to resolve it.
Glusterd was not checking if the Senders of requests it receives are in it's friend list before performing the friend state machine operations. We added the validations to fix that problem