Bug 1320020
Summary: | add-brick on a replicate volume could lead to data-loss | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Anuradha <atalur> |
Component: | replicate | Assignee: | Anuradha <atalur> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 3.7.9 | CC: | amukherj, bugs, sabose, sasundar, smohan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.10 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1276203 | Environment: | |
Last Closed: | 2016-04-19 07:00:16 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: | 1276203 | ||
Bug Blocks: | 1248998, 1258386, 1365455, 1366440, 1366444 |
Description
Anuradha
2016-03-22 07:00:31 UTC
REVIEW: http://review.gluster.org/13806 (glusterd / afr : Enable auto heal when replica count increases) posted (#1) for review on release-3.7 by Anuradha Talur (atalur) REVIEW: http://review.gluster.org/13807 (afr : Enable auto heal when replica count increases) posted (#1) for review on release-3.7 by Anuradha Talur (atalur) REVIEW: http://review.gluster.org/13806 (glusterd / afr : Enable auto heal when replica count increases) posted (#2) for review on release-3.7 by Anuradha Talur (atalur) COMMIT: http://review.gluster.org/13806 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit f5f43424994859f263165f0cdebedffd5f08fdcc Author: Anuradha Talur <atalur> Date: Wed Mar 16 10:55:09 2016 +0530 glusterd / afr : Enable auto heal when replica count increases Backport of http://review.gluster.org/12451 In replicate volumes, when a brick is added to a replicate group, heal to the new brick should be triggered. Also, the new brick should not be considered as source for healing till it is up to date. Previously, extended attributes had to be set manually on the bricks for this to happen. This patch is part 1 patch to automate this process. >Change-Id: I29958448618372bfde23bf1dac5dd23dba1ad98f >BUG: 1276203 >Signed-off-by: Anuradha Talur <atalur> >Reviewed-on: http://review.gluster.org/12451 >Reviewed-by: Atin Mukherjee <amukherj> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.com> >Reviewed-by: Ravishankar N <ravishankar> >Smoke: Gluster Build System <jenkins.com> Signed-off-by: Anuradha Talur <atalur> Conflicts: libglusterfs/src/globals.h xlators/mgmt/glusterd/src/glusterd-replace-brick.c Change-Id: Ica83592aab8edbe49e2bb9d8d4824cf5c76324b7 BUG: 1320020 Reviewed-on: http://review.gluster.org/13806 Smoke: Gluster Build System <jenkins.com> Tested-by: Anuradha Talur <atalur> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> COMMIT: http://review.gluster.org/13807 committed in release-3.7 by Raghavendra G (rgowdapp) ------ commit cf91abba2e6bf22794b04d143f226906e44bf5d5 Author: Anuradha Talur <atalur> Date: Tue Mar 22 14:03:38 2016 +0530 afr : Enable auto heal when replica count increases Backport of: http://review.gluster.org/12454 This patch is part two change to prevent data loss in a replicate volume on doing a add-brick operation. Problem: After doing add-brick, there is a chance that self heal might happen from the newly added brick rather than the source brick, leading to data loss. Solution: Mark pending changelogs on afr children for the new afr-child so that heal is performed in the correct direction. >Change-Id: I11871e55eef3593aec874f92214a2d97da229b17 >BUG: 1276203 >Signed-off-by: Anuradha Talur <atalur> >Reviewed-on: http://review.gluster.org/12454 >Smoke: Gluster Build System <jenkins.com> >Reviewed-by: Pranith Kumar Karampuri <pkarampu> >Tested-by: Pranith Kumar Karampuri <pkarampu> >CentOS-regression: Gluster Build System <jenkins.com> >NetBSD-regression: NetBSD Build System <jenkins.org> Change-Id: Iae6af44f97e612cb3ee8c642254ec3d15ac063f5 BUG: 1320020 Signed-off-by: Anuradha Talur <atalur> Reviewed-on: http://review.gluster.org/13807 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> 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.10, please open a new bug report. glusterfs-3.7.10 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-April/026164.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |