summaryrefslogtreecommitdiffstats
path: root/xlators/protocol/client/src
diff options
context:
space:
mode:
authorAnuradha <atalur@redhat.com>2015-06-05 16:46:39 +0530
committerPranith Kumar Karampuri <pkarampu@redhat.com>2015-06-27 04:27:09 -0700
commite28ac41c5ffc7b87f09b5bf2fe7f43cd4d4a5af5 (patch)
tree95ddb30342c6c2ace05cdd932ff737a8e10fbfd7 /xlators/protocol/client/src
parentea1039c177ec781506fdae01132a7a876620693f (diff)
glusterd/ afr : set afr pending xattrs on replace brick
Backport of: http://review.gluster.org/10076/ This patch is part one change to prevent data loss in a replicate volume on doing a replace-brick commit force operation. Problem: After doing replace-brick commit force, there is a chance that self heal happens from the replaced (sink) brick rather than the source brick leading to data loss. Solution: During the commit phase of replace brick, after old brick is brought down, create a temporary mount and perform setfattr operation (on virtual xattr) indicating AFR to mark the replaced brick as sink. As a part of this change replace-brick command is being changed to use mgmt_v3 framework rather than op-state-machine framework. Many thanks to Krishnan Parthasarathi for helping me out on this. Change-Id: If0d51b5b3cef5b34d5672d46ea12eaa9d35fd894 BUG: 1232173 Signed-off-by: Anuradha Talur <atalur@redhat.com> Reviewed-on: http://review.gluster.org/11253 Tested-by: NetBSD Build System <jenkins@build.gluster.org> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Ravishankar N <ravishankar@redhat.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Diffstat (limited to 'xlators/protocol/client/src')
0 files changed, 0 insertions, 0 deletions