Runbook #3 – Trobleshooting and SOPs for 3 Common Cassandra Errors

The article provides insights on optimizing Cassandra’s performance by properly using prepared statements and batch operations. Prepared statements can be used to cache query plans, while batches can combine multiple Data Manipulation Language (DML) statements to achieve atomicity and isolation. Discarding prepared statements does not lead to a noticeable load on the cluster, but it is best practice to monitor Cassandra’s system.log for warnings related to it. Improper usage of large batches by writing to several partitions can create a bottleneck on the coordinator node, leading to slow queries and unresponsive nodes. A well-constructed batch targeting a single partition can reduce client-server traffic and more efficiently update a table with a single row mutation.

Excerpted from the text – “Notable excerpt: “A well-constructed batch targeting a single partition can reduce client-server traffic and more efficiently update a table with a single row mutation. But batch operations that involve multiple nodes are a definite anti-pattern.”

”