[Bugs] [Bug 1557304] [Glusterd] Volume operations fail on a (tiered) volume because of a stale lock held by one of the nodes

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1557304



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19730 committed in release-3.10 by
"Shyamsundar Ranganathan" <srangana at redhat.com> with a commit message- glusterd
: introduce timer in mgmt_v3_lock

Problem:
In a multinode environment, if two of the op-sm transactions
are initiated on one of the receiver nodes at the same time,
there might be a possibility that glusterd  may end up in
stale lock.

Solution:
During mgmt_v3_lock a registration is made to  gf_timer_call_after
which release the lock after certain period of time

>Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
>BUG: 1499004
>Signed-off-by: Gaurav Yadav <gyadav at redhat.com>

Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
BUG: 1557304
Signed-off-by: Gaurav Yadav <gyadav at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hSN5436efS&a=cc_unsubscribe