In aws, I just grow the cluster 2x, then shrink away the old nodes via decommission. Mind you I am not dealing with TBs of data, just hundreds of gigs. Also, I have deployment automated with Cloud Formation and Priam. YMMV.
On Tue, Jun 13, 2017 at 2:22 PM Cogumelos Maravilha < cogumelosmaravi...@sapo.pt> wrote: > Simplest way of all, if you are using RF>=2 simple terminate the old > instance and create a new one. > Cheers. > > > On 13-06-2017 18:01, Rutvij Bhatt wrote: > > Nevermind, I misunderstood the first link. In this case, the replacement > would just be leaving the listen_address as is (to > InetAddress.getLocalHost()) and just start the new instance up as you > pointed out in your original answer Hannu. > > Thanks. > > On Tue, Jun 13, 2017 at 12:35 PM Rutvij Bhatt <rut...@sense.com> wrote: > >> Hannu/Nitan, >> >> 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 <hkro...@gmail.com> wrote: >> >>> Hello, >>> >>> So the local information about tokens is stored in the system keyspace. >>> Also the host id and all that. >>> >>> Also documented here: >>> >>> https://support.datastax.com/hc/en-us/articles/204289959-Changing-IP-addresses-in-DSE >>> >>> If for any reason that causes issues, you can also check this: >>> https://issues.apache.org/jira/browse/CASSANDRA-8382 >>> >>> 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 (ni...@bamlabs.com) 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 <hkro...@gmail.com> wrote: >>> >>> Cassandra automatically realizes that have just effectively changed IP >>> address >>> >>> >>> >
