|
| From: | Vijay Bellur |
| Subject: | Re: [Gluster-devel] deadlock? Unable to get lock for uuid which is held by itself |
| Date: | Sun, 26 Jan 2014 22:37:20 +0530 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 01/25/2014 06:27 PM, Yandong Yao wrote:
Hi Guys, I am using gluster 3.4.2 and doing some test with replica=4, and got following 'unable to get lock error', while it seems the lock has been acquired by itself already. is this a deadlock? any other volume command will be fail with error message like 'another transaction is in progress'.
The locking problem is related to the cluster wide locking done by glusterd for performing a volume operation. A restart of glusterd on all nodes can help in overcoming this problem.
Is there a sequence of steps that lead to this problem? -Vijay
| [Prev in Thread] | Current Thread | [Next in Thread] |