[Bugs] [Bug 1211866] Concurrently detaching a peer on one node and stopping glusterd on other node, leads to dead-lock on former node
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jan 25 05:45:43 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1211866
Byreddy <bsrirama at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2016-01-25 00:45:43
--- Comment #7 from Byreddy <bsrirama at redhat.com> ---
Checked this issue with latest 3.1.2 build ( glusterfs-3.7.5-17 ) on rhel7
1. Created two node cluster (N1 and N2)
2.Performed below steps using the terminator tool to broadcast commands
concurrently to 2 nodes.
a)On N1 > gluster peer detach N2
b)On N2 > systemctl stop glusterd
No issues observed and able to get the response for gluster commands issued on
N1.
Based on above verification details closing this bug as working in current
release.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Yw8i6U32f9&a=cc_unsubscribe
More information about the Bugs
mailing list