Bug 1288027
Summary: | [geo-rep+tiering]: symlinks are not getting synced to slave on tiered master setup | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Saravanakumar <sarumuga> |
Component: | geo-replication | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 3.7.6 | CC: | avishwan, bugs, chrisw, csaba, nchilaka, nlevinki, rhinduja, sankarshan, sarumuga, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1287519 | Environment: | |
Last Closed: | 2016-03-22 08:15:07 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: | 1286637, 1287519 | ||
Bug Blocks: |
Description
Saravanakumar
2015-12-03 10:41:29 UTC
REVIEW: http://review.gluster.org/12891 (geo-rep: use cold tier bricks for namespace operations) posted (#1) for review on release-3.7 by Saravanakumar Arumugam (sarumuga) REVIEW: http://review.gluster.org/12891 (geo-rep: use cold tier bricks for namespace operations) posted (#2) for review on release-3.7 by Saravanakumar Arumugam (sarumuga) COMMIT: http://review.gluster.org/12891 committed in release-3.7 by Venky Shankar (vshankar) ------ commit d3d2b6459c2a75534b137e1136a001184df79e2e Author: Saravanakumar Arumugam <sarumuga> Date: Wed Dec 2 14:26:47 2015 +0530 geo-rep: use cold tier bricks for namespace operations Problem: symlinks are not getting synced to slave in a Tiering based volume. Solution: Now, symlinks are created directly in cold tier bricks( in the backend). Earlier, cold tier was avoided for namespace operations and only hot tier was used while processing changelogs. Now, cold tier is HASH subvolume in a Tiering volume. So, carry out namespace operation only in cold tier subvolume and avoid hot tier subvolume to avoid any races. Earlier, XSYNC was used(and changeloghistory avoided) during initial sync in order to avoid race while processing historychangelog in Hot tier. This is no longer required as there is no race from Hot tier. Also, avoid both live and history changelog ENTRY operations from Hot tier to avoid any race with cold tier. Change-Id: Ia8fbb7ae037f5b6cb683f36c0df5c3fc2894636e BUG: 1288027 Signed-off-by: Saravanakumar Arumugam <sarumuga> Reviewed-on: http://review.gluster.org/12844 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Venky Shankar <vshankar> (cherry picked from commit 93f31189ce8f6e2980a39b02568ed17088e0a667) Reviewed-on: http://review.gluster.org/12891 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.7.7, please open a new bug report. glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |