[Bugs] [Bug 1322145] Glusterd fails to restart after replacing a failed GlusterFS node and a volume has a snapshot

[bugzilla at redhat.com]

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

Avra Sengupta <asengupt at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(rjoseph at redhat.co |
                   |m)                          |
                   |needinfo?(asengupt at redhat.c |
                   |om)                         |



--- Comment #16 from Avra Sengupta <asengupt at redhat.com> ---
I agree with Comment #11 from Atin. Snapshot volume is exactly like any other
gluster volume, when it comes to peer handshake. The fact that it is not
finding the IP in the cluster, which is in it's volfile will make it do a peer
reject.

As Atin suggested, the only option we have here is to change the IP in the
volfile with the snap. But even with that option, as gluster snapshots are COW
LVM based snapshots you end up losing your snapshot if it had any bricks in the
cluster member which was forcibly removed.

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