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@redhat.com>
            >Reviewed-on: http://review.gluster.org/12454
            >Smoke: Gluster Build System <jenkins@build.gluster.com>
            >Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
            >Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
            >CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
            >NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

Change-Id: Iae6af44f97e612cb3ee8c642254ec3d15ac063f5
BUG: 1320020
Signed-off-by: Anuradha Talur <atalur@redhat.com>
Reviewed-on: http://review.gluster.org/13807
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

0 files changed, 0 insertions, 0 deletions