Bug 1234882
Summary: | [geo-rep]: Feature fan-out fails with the use of meta volume config | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> | |
Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, chrisw, csaba, gluster-bugs, khiremat, nlevinki, rcyriac, rhinduja, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Regression, Reopened | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1234419 | |||
: | 1234898 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:15:21 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: | 1234419 | |||
Bug Blocks: | 1234898 |
Description
Kotresh HR
2015-06-23 12:47:01 UTC
REVIEW: http://review.gluster.org/11367 (geo-rep: Fix geo-rep fanout setup with meta volume) posted (#1) for review on master by Kotresh HR (khiremat) Patch is merged! Missed automatic upate. COMMIT: http://review.gluster.org/11367 geo-rep: Fix geo-rep fanout setup with meta volume Lock filename was formed with 'master volume id' and 'subvol number'. Hence multiple slaves try acquiring lock on same file and become PASSIVE ending up not syncing data. Using 'slave volume id' in lock filename will fix the issue making lock file unique across different slaves. BUG: 1234882 Change-Id: Ie3590b36ed03e80d74c0cfc1290dd72122a3b4b1 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11367 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Aravinda VK <avishwan> Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |