[Bugs] [Bug 1310972] After GlusterD restart, Remove-brick commit happening even though data migration not completed.

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 23 15:04:34 UTC 2016


--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13489 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
commit 28c2798d5e1f36e3f57192b693758fa8a9f26743
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Sat Jan 30 08:47:35 2016 +0530

    glusterd: set decommission_is_in_progress flag for inprogress remove-brick
op on glusterd restart

    Backport of http://review.gluster.org/13323

    While remove brick is in progress, if glusterd is restarted since
    flag is not persisted in the store the same value is not retained back
    in glusterd not blocking remove brick commit when rebalance is already in

    Change-Id: Ibbf12f3792d65ab1293fad1e368568be141a1cd6
    BUG: 1310972
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/13323
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga at redhat.com>
    Reviewed-on: http://review.gluster.org/13489

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=FvVJpVpvFx&a=cc_unsubscribe

More information about the Bugs mailing list