Hi team,
We are currently using 256 number of tokens.We are planning to change it to 32 or 16.Before that i would like to know more insights about the performance impact on the cluster if we keep the same number of tokens?
Regards
Mani Rangu
Hi team,
We are currently using 256 number of tokens.We are planning to change it to 32 or 16.Before that i would like to know more insights about the performance impact on the cluster if we keep the same number of tokens?
Regards
Mani Rangu
For the most part, a high num_tokens
is not so much an issue with performance but issues relating to:
For details, Anthony Grasso discussed these issues at length in his blog post The Impacts of Changing the Number of VNodes in Apache Cassandra where he also talked about the correct way of changing the virtual node configuration on an existing cluster. Cheers!
Hi! I would definitely recommend reducing the number of tokens. In older versions of dse and cassandra, 256 vnodes were recommended in order to better balance data load, but post 3.0 versions haven't had the same load issues.
Due to better node balancing algorithms (like using allocate tokens for replication factor in cassandra.yaml), we recommend decreasing the tokens to 8. By decreasing the tokens, you will seriously offload a lot of work from the node when bootstrapping and repairing simply because there will be far fewer sstables.
6 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use