A peer-to-peer communication protocol to discover and share location and state information about the other nodes in a Cassandra cluster. Gossip information is also persisted locally by each node to use immediately when a node restarts.
A partitioner determines which node will receive the first replica of a piece of data, and how to distribute other replicas across other nodes in the cluster.
Each row of data is uniquely identified by a primary key, which may be the same as its partition key, but which may also include other clustering columns.
A partitioner is a hash function that derives a token from the primary key of a row. The partitioner uses the token value to determine which nodes in the cluster receive the replicas of that row.
The Murmur3Partitioner is the default partitioning strategy for new Cassandra clusters and the right choice for new clusters in almost all cases.
You must set the partitioner and assign the node a num_tokens value for each node.The number of tokens you assign depends on the hardware capabilities of the system. If not using virtual nodes (vnodes), use the initial_token setting instead.
All replicas are equally important; there is no primary or master replica. You define the replication factor for each datacenter. Generally you should set the replication strategy greater than one, but no more than the number of nodes in the cluster.
Replica placement strategy Cassandra stores copies (replicas) of data on multiple nodes to ensure reliability and fault tolerance. A replication strategy determines which nodes to place replicas on. The first replica of data is simply the first copy; it is not unique in any sense. The NetworkTopologyStrategy is highly recommended for most deployments.
When creating a keyspace, you must define the replica placement strategy and the number of replicas you want.
SnitchA snitch defines groups of machines into datacenters and racks (the topology) that the replication strategy uses to place replicas.
You must configure a snitch when you create a cluster. All snitches use a dynamic snitch layer, which monitors performance and chooses the best replica for reading. It is enabled by default and recommended for use in most deployments. Configure dynamic snitch thresholds for each node in the cassandra.yaml configuration file.The GossipingPropertyFileSnitch is recommended for production.
The cassandra.yaml configuration file The main configuration file for setting the initialization properties for a cluster, caching parameters for tables, properties for tuning and resource utilization, timeout settings, client connections, backups, and security.
By default, a node is configured to store the data it manages in a directory set in the cassandra.yamlfile.
In a production cluster deployment, you can change the commitlog-directory to a different disk drive from the data_file_directories.
System keyspace table properties You set storage configuration attributes on a per-keyspace or per-table basis programmatically or using a client application, such as CQL.
Start-Up Ideas, Tech Code, Use Cases, Thoughts 