Hi In a 4 node cluster with replication factor 3 we have been using the default num_tokens=256 from Cassandra 3. We have upgraded to Cassandra 4.1 last year and planning on upgrading to 5 soon and we see that the recommendation has been changed to 16. An attempt to do a rolling build of the cluster with num_token=16 has failed since once I take down one of the old nodes most of the data arrives into the other old nodes which then become strained and at high risk of crashing. Each of the old nodes stores data of ~ 700GB. To my understanding the safest option is to setup a second DC and join it to the cluster then decommission the old one but I would like to understand how bad is it to keep the num_tokens at 256 and how will it affect practically in a day to day use in 4.1 and Cassandra 5. Thanks for any help, Isaeed Mohanna
Best regards, Isaeed Mohanna, Software Development Manager [cid:image001.png@01DBFB83.5825A030] Intelligent Cold Chain Monitoring E-Mail: isa...@xsense.co<mailto:isa...@xsense.co> | Web: www.xsense.co<http://www.xsense.co/> If you have further questions please don't hesitate to contact me.
