RE: [EXTERNAL] Re: Question on changing node IP address

["Durity, Sean R" <SE...@homedepot.com>]

This has not been my experience. Changing IP address is one of the worst admin tasks for Cassandra. System.peers and other information on each nodes is stored by ip address. And gossip is really good at sending around the old information mixed with new…



Sean Durity

From: Oleksandr Shulgin <ol...@zalando.de>
Sent: Tuesday, February 26, 2019 5:36 AM
To: User <us...@cassandra.apache.org>
Subject: [EXTERNAL] Re: Question on changing node IP address

On Tue, Feb 26, 2019 at 9:39 AM wxn002@zjqunshuo.com<ma...@zjqunshuo.com> <wx...@zjqunshuo.com>> wrote:

I'm running 2.2.8 with vnodes and I'm planning to change node IP address.
My procedure is:
Turn down one node, setting auto_bootstrap to false in yaml file, then bring it up with -Dcassandra.replace_address. Repeat the procedure one by one for the other nodes.

I care about streaming because the data is very large and if there is streaming, it will take a long time. When the node with new IP be brought up, will it take over the token range it has before? I expect no token range reassignment and no streaming. Am I right?

Any thing I need care about when making IP address change?

Changing the IP address of a node does not require special considerations.  After restart with the new address the server will notice it and log a warning, but it will keep token ownership as long as it keeps the old host id (meaning it must use the same data directory as before restart).

At the same time, *do not* use the replace_address option: it assumes empty data directory and will try to stream data from other replicas into the node.

--
Alex


________________________________

The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.

Re: [EXTERNAL] Re: Question on changing node IP address

[Oleksandr Shulgin <ol...@zalando.de>]

On Tue, Feb 26, 2019 at 3:26 PM Durity, Sean R <SE...@homedepot.com>
wrote:

> This has not been my experience. Changing IP address is one of the worst
> admin tasks for Cassandra. System.peers and other information on each nodes
> is stored by ip address. And gossip is really good at sending around the
> old information mixed with new…
>

Hm, on which version was it?  I might be biased not having worked with
anything but 3.0 since recently.

--
Alex