[Gluster-users] locking in 3.6.1

[Scott Merrill]

On 11/25/14, 10:11 AM, Scott Merrill wrote:
> On 11/25/14, 10:06 AM, Atin Mukherjee wrote:
>>
>>
>> On 11/25/2014 07:08 PM, Scott Merrill wrote:
>>> On 11/24/14, 11:56 PM, Atin Mukherjee wrote:
>>>> Can you please find/point out the first instance of the command and its
>>>> associated glusterd log which failed to acquire the cluster wide lock.
>>>
>>>
>>> Can you help me identify what I should be looking for in the logs?
>> grep for first instance of "locking failed" in glusterd log in the
>> server where the command failed.


This continues to be a problem for us.  Is there any common cause for
this?  Is there a common workaround that is suggested?

Or should we downgrade to Gluster 3.5?

Thanks.


> smerrill at gluster2:PRODUCTION:~> sudo grep "locking failed"
> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log*
> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log-20141124:[2014-11-19
> 19:05:19.312168] E [glusterd-syncop.c:105:gd_collate_errors] 0-:
> Unlocking failed on gluster1.innova.local. Please check log file for
> details.
> 
> smerrill at gluster3:PRODUCTION:~> sudo grep "locking failed"
> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log*
> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log-20141123:[2014-11-20
> 16:40:08.368442] E [glusterd-syncop.c:105:gd_collate_errors] 0-:
> Unlocking failed on gluster2.innova.local. Please check log file for
> details.
> 
> smerrill at gluster1:PRODUCTION:~> sudo grep "locking failed"
> /var/log/glusterfs/etc-glust-glusterd.vol.log*
> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log-20141124:[2014-11-22
> 02:10:09.795695] E [glusterd-syncop.c:105:gd_collate_errors] 0-:
> Unlocking failed on gluster2.innova.local. Please check log file for
> details.
>