What is the best practice to set write or read consistency as per number of nodes and RF factor ?
What is the best practice to set write or read consistency as per number of nodes and RF factor ?
We recommend configuring 3 replicas in each of the data centres in the cluster using NetworkTopologyStrategy
for high availability.
3 replicas allows for strong consistency using one of the quorum levels LOCAL_QUORUM
, EACH_QUORUM
and QUORUM
. A strong consistency level is recommended in almost all use cases with very few exceptions.
You can read more about it in the Data Replication and How consistency level is configured pages. Cheers!
5 People are following this question.
Why are results inconsistent when reading with consistency ALL compared to ONE?
Will data be stored on the same node if 2 tables have the same partition key?
How can I minimise the impact of a full table scan running Spark against Cassandra?
TOKEN() query returning "no viable alternative at input 'TOKEN()'"
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