Apache Cassandra 3.7 snitch issue cannot start data center

cassandra cannot start node if snitch's data center differs from previous data center
please fix the snitch configuration, decommission and rebootstrap this node or use the flag
cassandra ignore_dc
cassandra rebootstrap

I am using ubuntu 14.04 with apache cassandra 3.7. I am trying to start it but get the following error message:

ERROR [main] 2016-07-15 15:22:10,627 CassandraDaemon.java:731 - Cannot start node if snitch's data center (dc1) differs from previous data center (datacenter1). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true.

I know I can set -Dcassandra.ignore_dc=true, BUT that is not a fix, its a band-aid and for development use only, this is suppose to be in production. I tried to clear out all the files and folders in /var/lib/cassandra, I MEAN every SINGLE FILE AND FOLDER, started apache cassandra again, AND STILL THE SAME ERROR MESSAGE... any other idea??

change in file: /etc/cassandra/cassandra-rackdc.properties entry from dc1 to datacenter1 on all nodes and then do a rolling restart of nodes.

Cannot start node if snitch's data center (dc1) differs from previous , Cannot start node if snitch's data center (dc1) differs from previous data center posted by PRAJEETH on APR 10, 2016 under APACHE CASSANDRA. This is a problem reading the commitlog while starting. You should check if the file is perhaps empty or has wrong permissions. If there are more than this single node on your cluster - and you have a replication factor higher than one, simply delete this single commitlog file and try starting up cassandra again and run a repair.

If have just switched to GossipingPropertyFileSnitch, start Cassandra with the option


If it starts successfully, execute:

nodetool repair
nodetool cleanup

Afterwards, Cassandra should be able to start normally without the ignore option.

Multi-datacenter configuration, For details on starting Cassandra, see Manage Apache Cassandra in the API Gateway use the snitch-configured datacenter names used in cassandra- rackdc.properties . if the initial deployment did not set the multi-datacenter replication values. datacenters, and it would be difficult to know that an issue had occurred. -# Available implementations: -# org.apache.cassandra.cache.OHCProvider Fully off-heap row cache implementation (default). -# org.apache.cassandra.cache.SerializingCacheProvider This is the row cache implementation availabile -# in previous releases of Cassandra. -# row_cache_class_name: org.apache.cassandra.cache.OHCProvider - # Maximum size

I faced the issue while upgrading my Apache cassandra from 3.11.1 to 3.11.4 . cassandra.yaml

old_Config : endpoint_snitch: GossipingPropertyFileSnitch

New_Config: endpoint_snitch: SimpleSnitch

{changed it to GossipingPropertyFileSnitch}


old_version_config: dc:Dc1 rack:Rack1

New_version_config: dc:dc rack:rack (changed this to Dc1 and Rack1)

this resolves my issue

cassandra, Переходя от SimpleSnitch к PropertyFileSnitch или Gossiping, я преуспел, но процесс обратный не был. Закончился в этой точке: Cannot start node if� Unfortunately both releases 1.3.7 and 1.4.0 have subsequently been found to call a refresh service even when no changes had been made to the underlying configuration. In release 1.8.0 (somewhat belatedly) the service_refresh flag has been introduced to mitigate against similar problems. Issues When Upgrading to 1.3.7. Please see the notes for 1

Decommissioning a datacenter, Steps to properly remove a datacenter so no information is lost. DataStax Luna Enterprise Support for Apache Cassandra — Start a Free 30-Day Trial Now. Can't find what you're looking for? Steps for switching snitches. rack and data center information for the local node defined in the cassandra-rackdc.properties prefer_local=true - tells Cassandra to use the local IP address when communication is not across different data centers.

Expert Apache Cassandra Administration, Problems Posed by Relational Databases . Starting and Stopping the Multi- Node Cluster . Preventing a Keyspace from Sending Replicas to Some Data Centers . traditional relational databases cannot satisfy when handling very large data sets. [cqlsh 5.0.1 | Cassandra 3.7 | CQL spec 3.4.2 | Native protocol v4]. Cassandra pod seem to be up and running cassandra-1 2/2 Running 0 1h cassandra-2 2/2 Running 0 1h I'm also able to get Prometheus to scrape the metrics. But I'm not able to use cassandra. Janus cannot connect to it. It works fine with de

locp/cassandra � Installs Cassandra & DataStax Agent on RHEL , Create a Cluster in a Single Data Center; Create a Cluster in Multiple Data A Puppet module to install and manage Cassandra, DataStax Agent & OpsCenter Now that Cassandra 3 is available from the DataStax repositories, there is a problem Each node is configured to use the GossipingPropertyFileSnitch and 256� Apache Cassandra, supplying tools for Scylla. Contribute to scylladb/scylla-tools-java development by creating an account on GitHub.

  • Have you modified the cassandra.yaml/cassandra-env.sh files?
  • where do you add the option -Dcassandra.ignore_dc=true ?