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)

Summary

This chapter covered a broad range of subjects related to the Apache Cassandra nodetool utility. The commands covered here will help you to scale your cluster horizontally, as well as to remove and replace failed nodes. If you support a cluster that has nodes deployed in public or private cloud instances, you will find that it is often much faster to replace a failed node, than to try and resurrect it. To that end, you will find yourself using these tools and techniques often.

We discussed things such as taking snapshots, and incremental backups, as well as the maintenance associated with cleaning them up. It's important to remember that snapshots and backups taken are only valid for the data stored on a particular node. If the number of nodes exceeds your replication factor, you will likely have to maintain separate sets of off-cluster backup files for each node...