Re: Cassandra 2.1: replace running node without streaming

Good Point about the Rack - Kyrill! This makes total sense to me. Deleting the System Keyspace not really, If this contains all sensitive information about the node. Maybe this makes sense in conjunction with replace_node(at_first_boot) Option. Some comments from devs about this would be great.

Re: index_interval

I would also optimize for your worst case, which is hitting zero caches. If you're using the default settings when creating a table, you're going to get compression settings that are terrible for reads. If you've got memory to spare, I suggest changing your chunk_length_in_kb to 4 and disabling

Re: Cassandra 2.1: replace running node without streaming

I've found modified Carlos' article (more recent than that I was referring to) and this one contains the same method as you described, Oleksandr: https://mrcalonso.com/2016/01/26/cassandra-instantaneous-in-place-node-replacement Thank you for your readiness to help! Kind Regards, Kyrill

Re: Node won't start

Thanks Alex. That’s exactly what I ended up doing - it did take maybe 45m to come back up though :( -B Sent from my iPhone > On Feb 3, 2018, at 9:03 AM, Alexander Dejanovski > wrote: > > Hi Brian, > > I just tested this on a CCM cluster and the node started

Re: Node won't start

Hi Brian, I just tested this on a CCM cluster and the node started without problem. It flushed some new SSTables a short while after. I honestly do not know the specifics of how size_estimates is used, but if it prevented a node from restarting I'd definitely remove the sstables to get it back

Node won't start

Hi guys, I've got a 2.1.15 node that will not start it seems. Hangs on Opening system.size_estimates. Sometimes it can take a while but I've let it run for 90m and nothing. Should I move this sstable out of the way to let it start? will it rebuild/refresh size estimates if I remove that

Re: Cassandra 2.1: replace running node without streaming

Thank you Oleksandr, Just tested on 3.11.1 and it worked for me (you may see the logs below). Just comprehended that there is one important prerequisite this method to work: new node MUST be located in the same rack (in terms of C*) as the old one. Otherwise correct replicas placement order

Re: Cassandra 2.1: replace running node without streaming

On 3 Feb 2018 08:49, "Jürgen Albersdorfer" wrote: Cool, good to know. Do you know this is still true for 3.11.1? Well, I've never tried with that specific version, but this is pretty fundamental, so I would expect it to work the same way. Test in isolation if you want