All geek questions in one place

Failed to start dse solr node

I am trying datastax enterprise 4.8.4 on ubuntu. Installation is in accordance with the instructions. I can start cassandra node using the sudo service dse start . Then I want to try restarting as a solr node on the same computer. So I edit /etc/default/dse and set SOLR_ENABLED=1 . Now I tried to start cassandra again, it failed.

 @ubuntu:~$ sudo service dse start * Starting DSE daemon dse DSE daemon starting with Solr enabled (edit /etc/default/dse to disable) [ OK ] @ubuntu:~$ sudo service dse status * dse is running @ubuntu:~$ sudo service dse status * dse is not running

I checked /var/log/cassandra/system.log . Here is the error message:

 ERROR [main] 2016-01-28 16:44:02,767 CassandraDaemon.java:294 - Fatal exception during initialization org.apache.cassandra.exceptions.ConfigurationException: Cannot start node if snitch data center (Solr) differs from previous data center (Cassandra). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true.

The question is, how can I fix this? or where can I add -Dcassandra.ignore_dc=true ?

+5
source share
2 answers

From 2.1.13 you are not allowed to change the data center of an existing node. This is to protect users from manufacturing errors, as changing the names of data centers (DC) in a live system will result in downtime.

DSE Simple Snitch assigns nodes to logical data centers based on the type of workload. I.E. solr nodes will be added to DC DC sol; Cassandra nodes will be added to the Cassandra data center. If you change the type of workload using DSE simple snitch, you will change the DC name, which is not allowed by default.

If this is a test environment and you know what you are doing (you are ready to take the downtime when all the nodes in your DC change to a new DC), you can send the following jvm flag in your cassandra-env.sh file

-Dcassandra.ignore_rack = true and / or

-Dcassandra.ignore_dc = true.

** make sure your topology remains the same after changing the DC / name, otherwise replication may be confused, and you can get a lot of streaming + CPU + io + obsolete reads **

+10
source

Below are the steps you can take to solve the problem -

Error: - CassandraDaemon.java:709 - Cannot start the node if the Snitch data center (Cassandra) is different from the previous data center (SearchGraphAnalytics).

Solution : -

  • Change the network topology to GossipingPropertyFileSnitch with SimpleSnitch in the Cassandra.yaml file located in / usr / share / dse / resource / cassandra / conf (if set to not running the service)

  • Create a properties file with data center and rack data if it does not exist.

    • Path: / usr / share / dse / resource / cassandra / conf

    • filename: cassandra-rackdc.properties

    And add the following entries -

     --indicate the rack and dc for this node dc=SearchGraphAnalytics // the previous name of your DC before upgrading rack=RAC1

  • If the Gremlin server error persists, run the chart using the options below -

    This error can occur if DataStax Enterprise was installed from tarball or from the DataStax installer with the No Services option.

    Run dse using the following options: -

     /usr/share/dse$ bin/cassandra -g -s -k
0
source

Source: https://habr.com/ru/post/1241695/

More articles:


All Articles