Bug 1499004
Summary: | [Glusterd] Volume operations fail on a (tiered) volume because of a stale lock held by one of the nodes | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Gaurav Yadav <gyadav> | |
Component: | glusterd | Assignee: | Gaurav Yadav <gyadav> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | amukherj, asriram, bkunal, bmohanra, bsrirama, bturner, bugs, olim, pousley, rcyriac, rhs-bugs, sanandpa, sbairagy, storage-qa-internal, vbellur | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.13.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1425681 | |||
: | 1503239 1557304 (view as bug list) | Environment: | ||
Last Closed: | 2017-12-08 17:42:08 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1425681, 1503239, 1557304 |
Description
Gaurav Yadav
2017-10-05 19:06:41 UTC
REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#2) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#3) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#4) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#5) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#6) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#7) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#8) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#9) for review on master by Gaurav Yadav (gyadav) REVIEW: https://review.gluster.org/18437 (glusterd : introduce timer in mgmt_v3_lock) posted (#10) for review on master by Atin Mukherjee (amukherj) COMMIT: https://review.gluster.org/18437 committed in master by Atin Mukherjee (amukherj) ------ commit 614904fa7a31bf6f69074238b7e710a20e05e1bb Author: Gaurav Yadav <gyadav> Date: Thu Oct 5 23:44:46 2017 +0530 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> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/ |