[Bugs] [Bug 1297305] [GlusterD]: Peer detach happening with a node which is hosting volume bricks

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 14 09:35:09 UTC 2016


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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13210 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit a7b399fd0ef928c2cca4092b00edb21e70c59f62
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Mon Dec 21 23:13:43 2015 +0530

    glusterd: import/export brickinfo->uuid

    Backport of http://review.gluster.org/#/c/13047/

        Given a two node cluster with node N1 & N2, if a dummy node N3 is peer
probed, the
        probed node N3  goes for importing volumes from the probing node (N1),
but
        it still doesn't have information about the other node (N2) about its
membership
        (since peer update happens post volume updates) and hence fail to
update its
        brick's uuid. Post that even though N2 updates N3 about its membership
the
        brick's uuid was never generated. Now as a consequence when N3
initiates a
        detach of N2, it checks whether the node to be detached has any bricks
        configured by its respective uuid which is NULL in this case and hence
it goes
        ahead and removes the peer which ideally it shouldn't have (refer to
        glusterd_friend_contains_vol_bricks () for the logic)

        Fix is to export brick's uuid and import it at the probed node instead
of
        resolving it.

    Change-Id: I2d88c72175347550a45ab12aff0ae248e56baa87
    BUG: 1297305
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/13047
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Reviewed-by: Avra Sengupta <asengupt at redhat.com>
    Reviewed-on: http://review.gluster.org/13210

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


More information about the Bugs mailing list