Re: Migrating Cassandra from 3.11.11 to 4.0.0 vs num_tokens

Won't option 2 in that list potentially cause some pretty severe load imbalance in most cases? The last node with 256 tokens will end up with 16x as much data on it as the 16 token nodes, right? You'd have to mitigate it either by adding 16 new nodes for every one you replace except the last one,

Re: [UPGRADATION] Apache Cassandra from version 3.0.9 to 4.0.0

Hi Jeff, *When you’re upgrading or rebuilding you want all copies on the same version with proper sstables . So either add GCP then upgrade to 4.0 or upgrade to 4.0 and then expand to GCP. Don’t do them at the same time.* I think I forgot to mention one thing that after completion of step 1 our G

Re: [UPGRADATION] Apache Cassandra from version 3.0.9 to 4.0.0

In-line > On Sep 3, 2021, at 11:12 AM, MyWorld wrote: > >  > Hi Jeff, > Thanks for your response. > To answer your question, Yes, we have created dev environment by restoring > them from snapshot/CSV files. > > Just one follow up question, I have a 5-node single DC on production on > versio

Re: Migrating Cassandra from 3.11.11 to 4.0.0 vs num_tokens

Hi Jean, This is a really good question. As Erick mentioned, if you want to change your cluster's *num_tokens* to 16 to match the 4.0 default, you will need to perform a datacenter migration. Feel free to read over this blog post