Book Image

Mastering Apache Cassandra 3.x - Third Edition

By : Aaron Ploetz, Tejaswi Malepati, Nishant Neeraj
Book Image

Mastering Apache Cassandra 3.x - Third Edition

By: Aaron Ploetz, Tejaswi Malepati, Nishant Neeraj

Overview of this book

With ever-increasing rates of data creation, the demand for storing data fast and reliably becomes a need. Apache Cassandra is the perfect choice for building fault-tolerant and scalable databases. Mastering Apache Cassandra 3.x teaches you how to build and architect your clusters, configure and work with your nodes, and program in a high-throughput environment, helping you understand the power of Cassandra as per the new features. Once you’ve covered a brief recap of the basics, you’ll move on to deploying and monitoring a production setup and optimizing and integrating it with other software. You’ll work with the advanced features of CQL and the new storage engine in order to understand how they function on the server-side. You’ll explore the integration and interaction of Cassandra components, followed by discovering features such as token allocation algorithm, CQL3, vnodes, lightweight transactions, and data modelling in detail. Last but not least you will get to grips with Apache Spark. By the end of this book, you’ll be able to analyse big data, and build and manage high-performance databases for your application.
Table of Contents (12 chapters)

Write performance

Given its log-based storage model and memtable/commitlog design, Apache Cassandra usually does very well when it comes to high-performance data-ingestion. That being said, it is not uncommon to hear of application teams complaining about Cassandra nodes being saturated with load due to writes. Here is a short list of things to check when write performance suffers.

Commitlog mount point

One piece of advice, going back to the early days of Apache Cassandra, was to ensure that the commitlog was on a different physical mount point than the data drives. This is because disk I/O could become bottlenecked at the device level during periods of heavy writes. Putting the commitlog and data directories on separate mount...