Red Hat Bugzilla – Full Text Bug Listing
|Summary:||glusterd lockup recovery.|
|Product:||[Community] GlusterFS||Reporter:||Harshavardhana <fharshav>|
|Component:||glusterd||Assignee:||Pranith Kumar K <pkarampu>|
|Status:||CLOSED DUPLICATE||QA Contact:|
|Version:||3.1.1||CC:||cww, gluster-bugs, vijay|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Harshavardhana 2010-12-05 02:14:17 EST
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 17:39:11 EST
(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.