[Bugs] [Bug 1211866] New: 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

            Bug ID: 1211866
           Summary: Detaching a peer on one node and stopping glusterd on
                    other node, leads to dead-lock on former node
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: sasundar at redhat.com
        QA Contact: sasundar at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
-----------------------
In a 2 node gluster cluster, from node1 peer detach node2 and from node2 stop
glusterd. And this lead to deadlock in node1 consistently

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.7 nightly ( glusterfs-3.7dev-0.994.gitf522001.el6.x86_64 )

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Create a 2 node cluster ( say, node1, node2 )
2. Perform following steps concurrently. I used TERMINATOR tool to broadcast
commands concurrently to 2 node
3. On node1, execute - "gluster peer detach <node2>"
4. On node2, execute - "service glusterd stop"

Actual results:
---------------
All the commands executed on node1, resulted in "Error: cli timeout"

Expected results:
-----------------
There shouldn't be any problem in executing gluster commands

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