[Bugs] [Bug 1628605] New: One client hangs when another client loses communication with bricks during intensive write I /O

[bugzilla at redhat.com]

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

            Bug ID: 1628605
           Summary: One client hangs when another client loses
                    communication with bricks during intensive write I/O
           Product: GlusterFS
           Version: mainline
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org



Description of problem:

Bricks don't detect abrupt client disconnections in a reasonable time. If this
happens when the dead client had locks held, accessing the locked file from
other clients will take a huge amount of time.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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