Scott,
We have identified a grey area in the code which is causing this issue.
FYI, fix has been sent in master - http://review.gluster.org/#/c/9269/
Once this patch is in master streamline I will backport it in 3.6 branch.
~Atin
On 12/12/2014 08:28 PM, Scott Merrill wrote:
> On 11/25/14, 10:11
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
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.
>>
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 lookin
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?
I restarted the glusterd service and
Scott,
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.
There are few cases related to rebalance commands where we may end up
having stale locks, have you performed rebalance in between?
~Atin
On 11/25/
+glusterd folks.
Pranith
On 11/25/2014 02:41 AM, Scott Merrill wrote:
After upgrading to Gluster 3.6.1, I'm seeing a lot more (stale?) locks
between my replicated servers. This prevents me from executing commands
on either server.
From one server:
root@gluster1:PRODUCTION:~> gluster volume st
After upgrading to Gluster 3.6.1, I'm seeing a lot more (stale?) locks
between my replicated servers. This prevents me from executing commands
on either server.
>From one server:
root@gluster1:PRODUCTION:~> gluster volume status epa
Locking failed on gluster2.domain.local. Please check log file f
