cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rutvij Bhatt <>
Subject Re: Node replacement strategy with AWS EBS
Date Tue, 13 Jun 2017 16:35:52 GMT

Thanks for your help so far! From what you said in your first response, I
can get away with just attaching the EBS volume to Cassandra and starting
it with the old node's private IP as my listen_address because it will take
over the token assignment from the old node using the data files? With
regards to "Cassandra automatically realizes that have just effectively
changed IP address.", it says in the first link to change this manually to
the desired address - does this not apply in my case if I'm replacing the
old node?

As for the plan I outlined earlier, is this more for DR scenarios where I
have lost a node due to hardware failure and I need to recover the data in
a safe manner by requesting a stream from the other replicas?  Am I
understanding this right?

On Tue, Jun 13, 2017 at 11:59 AM Hannu Kröger <> wrote:

> Hello,
> So the local information about tokens is stored in the system keyspace.
> Also the host id and all that.
> Also documented here:
> If for any reason that causes issues, you can also check this:
> If you copy all cassandra data, you are on the safe side. Good point in
> the links is that if you have IP addresses in topolgy or other files, then
> update those as well.
> Hannu
> On 13 June 2017 at 11:53:13, Nitan Kainth ( wrote:
> Hannu,
> "Cassandra automatically realizes that have just effectively changed IP
> address” —> are you sure C* will take care of IP change as is? How will it
> know which token range to be assigned to this new IP address?
> On Jun 13, 2017, at 10:51 AM, Hannu Kröger <> wrote:
> Cassandra automatically realizes that have just effectively changed IP
> address

View raw message