Cassandra Snitch Configuration

The snitch determines how Cassandra maps nodes to datacenters and racks.

Available Snitches

Snitch	Use Case
SimpleSnitch	Single DC, no rack awareness
GossipingPropertyFileSnitch	Production (recommended)
PropertyFileSnitch	Legacy
Ec2Snitch	AWS single region
Ec2MultiRegionSnitch	AWS multi-region
GoogleCloudSnitch	GCP
RackInferringSnitch	IP-based inference

endpoint_snitch: GossipingPropertyFileSnitch

dc=datacenter1
rack=rack1

# Optional
prefer_local=true
dc_suffix=_analytics

# Node in DC1
dc=us-east
rack=rack1

# Node in DC2
dc=eu-west
rack=rack1

endpoint_snitch: Ec2Snitch

# Automatic:
# DC = region (us-east-1)
# Rack = availability zone (us-east-1a)

endpoint_snitch: Ec2MultiRegionSnitch
listen_address: <private_ip>
broadcast_address: <public_ip>

endpoint_snitch: GoogleCloudSnitch

# Automatic:
# DC = project:region
# Rack = zone

# 1. Update cassandra.yaml on all nodes
# 2. Update cassandra-rackdc.properties
# 3. Rolling restart cluster
# 4. Run repair

nodetool repair -full

# Check datacenter/rack assignment
nodetool status

# Detailed gossip info
nodetool gossipinfo | grep -E "DC|RACK"