[Gluster-users] Cluster locked?

[Vijay Bellur]

On 05/17/2014 11:07 AM, B.K.Raghuram wrote:
> How does one figure out which node is holding the lock? A restart of
> glusterd on all the nodes in the pool did not seem to resolve the problem.
>

Checking the glusterd log will usually provide a hint regarding the uuid 
of the node that has a stale lock.

-Vijay

>
> On Fri, May 16, 2014 at 5:39 PM, Vijay Bellur <vbellur at redhat.com
> <mailto:vbellur at redhat.com>> wrote:
>
>     On 05/16/2014 12:24 PM, B.K.Raghuram wrote:
>
>         A hard accidental power down of our boxes now results in the message
>         "Another transaction could be in progress. Please try again after
>         sometime." for most volume operations. I'm presuming this is the
>         result
>         of some sort of cluster lock. How does one get around the
>         problem? Where
>         are such lock files stored?
>
>
>     The cluster lock is a lock that is in memory and is not persisted. A
>     restart of glusterd on the node that holds a stale lock would be
>     helpful to recover from this state.
>
>     Regards,
>     Vijay
>
>