Bug 763925 (GLUSTER-2193) - glusterd lockup recovery.
Summary: glusterd lockup recovery.
Keywords:
Status: CLOSED DUPLICATE of bug 765052
Alias: GLUSTER-2193
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1.1
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-05 07:14 UTC by Harshavardhana
Modified: 2015-03-23 01:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: ---
Documentation: DNR
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Harshavardhana 2010-12-05 07:14:17 UTC 
Once in a while due to network issues gluster cli locks up the whole trusted cluster of nodes. 

This makes subsequent gluster cli commands to fail.  Need to way to jumpstart all  the process by relinquishing the locks held.
Comment 1 Harshavardhana 2011-01-26 22:39:11 UTC 
(In reply to comment #0)
> Once in a while due to network issues gluster cli locks up the whole trusted
> cluster of nodes. 
> 
> This makes subsequent gluster cli commands to fail.  Need to way to jumpstart
> all  the process by relinquishing the locks held.


This is a scenario which we hit almost everyday. 

Node1 is editing volume graph by holding a lock, simultaneously another node tries to delete another volume results in a clash of locks. Latter node just locks up and never comes out of it. 

There is a need for "gluster cli" to be easily relinquish and communicate properly the locks to its friends.
Comment 2 Harshavardhana 2011-08-15 16:06:48 UTC 

*** This bug has been marked as a duplicate of bug 3320 ***
Note You need to log in before you can comment on or make changes to this bug.