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

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1303269



--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13323 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 3ca140f011faa9d92a4b3889607fefa33ae6de76
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

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

    Change-Id: Ibbf12f3792d65ab1293fad1e368568be141a1cd6
    BUG: 1303269
    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>

-- 
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=KBhwhsMrUB&a=cc_unsubscribe