Bug 803365 - Server send lock reply failure causes stale locks on server
Summary: Server send lock reply failure causes stale locks on server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-14 14:38 UTC by Junaid
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:50:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Junaid 2012-03-14 14:38:09 UTC 
Description of problem:
When lock self healing is "on", a network disconnect while sending a response to a lock fop will lead to stale locks on the server if a reconnection happens within the grace-timeout.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Anand Avati 2012-03-19 15:11:50 UTC 
CHANGE: http://review.gluster.com/2947 (protocol/server: Handle server send reply failure gracefully.) merged in master by Vijay Bellur (vijay)
Note You need to log in before you can comment on or make changes to this bug.