[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]

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

SATHEESARAN <sasundar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|CURRENTRELEASE              |WORKSFORME



--- Comment #8 from SATHEESARAN <sasundar at redhat.com> ---
(In reply to Byreddy from comment #7)
> 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.

Thanks Byreddy for verifying this issue with the latest RHGS 3.1.2 nightly
build.
I will re-open this bz, if the issue happens again

-- 
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=1hlXtxeuUO&a=cc_unsubscribe