The PropertyFileSnitch uses the for datacenters and rack names and to determine network topology so that requests are routed efficiently and allows the database to distribute replicas evenly.


This snitch determines proximity as determined by rack and datacenter. It uses the network details located in the file. When using this snitch, you can define your datacenter names to be whatever you want. Make sure that the datacenter names correlate to the name of your datacenters in the keyspace definition. Every node in the cluster should be described in the file, and this file should be exactly the same on every node in the cluster.

Setting datacenters and rack names

If you had non-uniform IPs and two physical datacenters with two racks in each, and a third logical datacenter for replicating analytics data, the file might look like this:

Datacenter and rack names are case-sensitive.

# datacenter One

# datacenter Two

# Analytics Replication Group

# default for unknown nodes
default =DC3:RAC1

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,