Gluster locked up when starting nodes in Docker pods
Issue
When starting gluster nodes in Docker pods, the cluster would deadlock when the second node was started. These messages are thrown:
[2019-06-12 15:11:30.594022] W [glusterd-locks.c:845:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0x2430a) [0x7fc439e5530a] -->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0x2e540) [0x7fc439e5f540] -->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0xe8573) [0x7fc439f19573] ) 0-management: Lock for vol vol_ffe63873fcb43af3107a408109ba6acc not held
[2019-06-12 15:11:30.594027] W [MSGID: 106117] [glusterd-handler.c:6407:__glusterd_peer_rpc_notify] 0-management: Lock not released for vol_ffe63873fcb43af3107a408109ba6acc
[2019-06-12 15:11:30.594038] W [glusterd-locks.c:845:glusterd_mgmt_v3_unlock] (-->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0x2430a) [0x7fc439e5530a] -->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0x2e540) [0x7fc439e5f540] -->/usr/lib64/glusterfs/4.1.2/xlator/mgmt/glusterd.so(+0xe8573) [0x7fc439f19573] ) 0-management: Lock for vol vol_fffd3c36400974e533e3c16d8137266f not held
[2019-06-12 15:11:30.594043] W [MSGID: 106117] [glusterd-handler.c:6407:__glusterd_peer_rpc_notify] 0-management: Lock not released for vol_fffd3c36400974e533e3c16d8137266f
Environment
Community-based gluster running in Docker pods
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
