Illustration Image

Cassandra.Link

The best knowledge base on Apache Cassandra®

Helping platform leaders, architects, engineers, and operators build scalable real time data platforms.

7/24/2018

Reading time:1 min

Cassandra Parameters for Dummies

by John Doe

This simple form allows you to try out different values for your Apache Cassandra clusterand see what the impact is for your application.Cluster size Replication Factor Write Level Read Level Your reads are"Consistent" means that for this particular Read/Write level combo, all nodes will "see" the same data. "Eventually consistent" means that you might get old data from some nodes and new data for others until the data has been replicated across all devices. The idea is that this way you can increase read/write speeds and improve tolerance against dead nodes.You can survive the loss of without impacting the application.How many nodes can go down without application noticing? This is a lower bound - in large clusters, you could lose more nodes and if they happen to be handling different parts of the keyspace, then you wouldn't notice either.You can survive the loss of without data loss.How many nodes can go down without physically losing data? This is a lower bound - in large clusters, you could lose more nodes and if they happen to be handling different parts of the keyspace, then you wouldn't notice either.You are really reading from every time.The more nodes you read from, more network traffic ensues, and the bigger the latencies involved. Cassandra read operation won't return until at least this many nodes have responded with some data value.You are really writing to every time.The more nodes you write to, more network traffic ensues, and the bigger the latencies involved. Cassandra write operation won't return until at least this many nodes have acknowledged receiving the data.Each node holds of your data.The bigger your cluster is, the more the data gets distributed across your nodes. If you are using the RandomPartitioner, or are very good at distributing your keys when you use OrderedPartitioner, this is how much data each of your nodes has to handle. This is also how much of your keyspace becomes inaccessible for each node that you lose beyond the safe limit, above.

Illustration Image

This simple form allows you to try out different values for your Apache Cassandra cluster and see what the impact is for your application.


Your reads are

"Consistent" means that for this particular Read/Write level combo, all nodes will "see" the same data. "Eventually consistent" means that you might get old data from some nodes and new data for others until the data has been replicated across all devices. The idea is that this way you can increase read/write speeds and improve tolerance against dead nodes.

You can survive the loss of without impacting the application.

How many nodes can go down without application noticing? This is a lower bound - in large clusters, you could lose more nodes and if they happen to be handling different parts of the keyspace, then you wouldn't notice either.

You can survive the loss of without data loss.

How many nodes can go down without physically losing data? This is a lower bound - in large clusters, you could lose more nodes and if they happen to be handling different parts of the keyspace, then you wouldn't notice either.

You are really reading from every time.

The more nodes you read from, more network traffic ensues, and the bigger the latencies involved. Cassandra read operation won't return until at least this many nodes have responded with some data value.

You are really writing to every time.

The more nodes you write to, more network traffic ensues, and the bigger the latencies involved. Cassandra write operation won't return until at least this many nodes have acknowledged receiving the data.

Each node holds of your data.

The bigger your cluster is, the more the data gets distributed across your nodes. If you are using the RandomPartitioner, or are very good at distributing your keys when you use OrderedPartitioner, this is how much data each of your nodes has to handle. This is also how much of your keyspace becomes inaccessible for each node that you lose beyond the safe limit, above.

Related Articles

cassandra
tools
sstables

ic-tools for Apache Cassandra SSTables

John Doe

2/17/2023

cassandra
tools

Checkout Planet Cassandra

Claim Your Free Planet Cassandra Contributor T-shirt!

Make your contribution and score a FREE Planet Cassandra Contributor T-Shirt! 
We value our incredible Cassandra community, and we want to express our gratitude by sending an exclusive Planet Cassandra Contributor T-Shirt you can wear with pride.

Join Our Newsletter!

Sign up below to receive email updates and see what's going on with our company

Explore Related Topics

AllKafkaSparkScyllaSStableKubernetesApiGithubGraphQl

Explore Further

packages