[Bugs] [Bug 1362170] Disconnection Issues in glusterd

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1362170

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
First of all 3.6 is not going to receive any bug fixes any further, please
refer to http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html .
You'd need to upgrade your cluster to 3.7/3.8.

Now coming to the relevant glusterd log here is what I think:

/usr/lib64/glusterfs/glusterfs/3.6.9/xlator/mgmt/glusterd.so(glusterd_mgmt_v3_unlock+0x356)[0x7f9df8acc1f5]
(-->
/usr/lib64/glusterfs/glusterfs/3.6.9/xlator/mgmt/glusterd.so(__glusterd_peer_rpc_notify+0x289)[0x7f9df8a2da4b]
(-->
/usr/lib64/glusterfs/glusterfs/3.6.9/xlator/mgmt/glusterd.so(glusterd_big_locked_notify+0x61)[0x7f9df8a22384]
(-->
/usr/lib64/glusterfs/glusterfs/3.6.9/xlator/mgmt/glusterd.so(glusterd_peer_rpc_notify+0x38)[0x7f9df8a2dbea]
))))) 0-management: Lock for vol services not held
The message "I [MSGID: 106006]
[glusterd-handler.c:4290:__glusterd_nodesvc_rpc_notify] 0-management: nfs has
disconnected from glusterd." repeated 39 times between [2016-07-18
07:58:08.475445] and [2016-07-18 08:00:06.414826]

This is expected and on a peer disconnect glusterd tries to release all the
stale locks, if the lock is not held by the peer for the volume(s) warning logs
are captured.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.