Essential information for understanding and using Cassandra.

Cassandra uses a protocol called gossip to discover location and state information about the other nodes participating in a Cassandra cluster.

How data is distributed and factors influencing replication.

A partitioner determines how data is distributed across the nodes in the cluster (including replicas).

A snitch determines which data centers and racks nodes belong to.

A description about Cassandra's storage structure and engine.

Understanding how Cassandra stores data.

Topics about how up-to-date and synchronized a row of data is on all replicas.

Choosing appropriate hardware depends on selecting the right balance of the following resources: memory, CPU, disks, number of nodes, and network.

Important information for deploying a production Cassandra cluster on Amazon EC2.

Determining how much data your Cassandra partitions can hold.

Determining how much data your Cassandra nodes can hold.

Accounting for storage overhead in determining user data size.

Implementation or design patterns that are ineffective and/or counterproductive in Cassandra production installations. Correct patterns are suggested in most cases.

About installing on Windows systems.

Steps for installing the same version as other nodes in your cluster.

Steps for uninstalling Cassandra.

Installing Cassandra on cloud providers.

Recommendations for production environments.

Configuration files directory locations.

The cassandra.yaml file is the main configuration file for Cassandra.

Set environment variables (cassandra.in.bat).

Topics for securing Cassandra.

Using the cassandra.yaml file to configure gossip.

Analyzing the heap dump file can help troubleshoot memory problems.

Topics about configuring virtual nodes.

Steps for configuring Cassandra for multiple network interfaces or when using different regions in cloud implementations.

Cassandra logging functionality using Simple Logging Facade for Java (SLF4J) with a logback backend.

Cassandra provides commit log archiving and point-in-time recovery.

If not using virtual nodes (vnodes), you must calculate tokens for your cluster.

Cassandra support for integrating Hadoop with Cassandra.

A deployment scenario for a Cassandra cluster with a single data center.

A deployment scenario for a Cassandra cluster with multiple data centers.

Steps for starting or stopping the Cassandra Windows service.

Remove all data from a Windows installations.

Clearing the data for an Amazon Machine Image restart.

Topics for adding or removing nodes, data centers, or clusters.

Cassandra backs up data by taking a snapshot of all on-disk data files (SSTable files) stored in the data directory.

Node repair topics.

Monitoring topics.

Tuning the Java Virtual Machine (JVM) can improve performance or reduce high memory consumption.

Data caching topics.

Configuring memtable throughput to improve write performance.

Steps for configuring compaction. The compaction process merges keys, combines columns, evicts tombstones, consolidates SSTables, and creates a new index in the merged SSTable.

Compression maximizes the storage capacity of Cassandra nodes by reducing the volume of data on disk and disk I/O, particularly for read-dominated workloads.

Enabling write survey mode.

Cassandra uses Bloom filters to determine whether an SSTable has data for a particular row.

Solutions for migrating from other databases.

Correcting a problem in the gossip state.

A command line interface for managing a cluster.

Cassandra start-up parameters can be run from the command line or specified in the cassandra-env.ps1 file.

A Java-based stress testing utility for basic benchmarking and load testing a Cassandra cluster.

The cluster's IO capacity is not enough to handle the write load it is receiving.

Some portion of the JVM is being swapped out by the operating system (OS).

Nodes are dying with OutOfMemory exceptions.

Nodetool commands can be run locally but not on other nodes in the cluster.

Check for and resolve schema disagreements.

Indicates that the ring is in a bad state.

Steps to configure the default idle connection timeout.