DataStax Academy FAQ

DataStax Academy migrated to a new learning management system (LMS) in July 2020. We are also moving to a new Cassandra Certification process so there are changes to exam bookings, voucher system and issuing of certificates.

Check out the Academy FAQ pages for answers to your questions:


question

william.pulling_194398 avatar image
william.pulling_194398 asked ·

Unable to see second added DSE node on local network

Unable to see second node 6.8.2 with 2 ubuntu 20.04 desktop machines on local network

172.16.0.20 runs fine as single node & can ping 172.16.0.14

172.16.0.14 also runs fine as single node & can ping 172.16.0.20.

cassandra.yaml

  • 'Kirkwood' as cluster name in both
  • seeds: "172.16.0.20,172.16.0.14"
  • listen_address as 172.16.0.20 or 172.16.0.14 respectively
  • native_transport_address as 172.16.0.20 or 172.16.0.14 respectively

cassandra-env.sh

  • JVM_OPTS=“$JVM_OPTS -Dcassandra.ignore_dc=true”


  • iptables -A INPUT -p tcp --dport 22 -j ACCEPT
  • iptables -A INPUT -p tcp --dport 80 -j ACCEPT
  • iptables -A INPUT -p tcp --dport 443 -j ACCEPT
  • iptables -A INPUT -p tcp -s 172.16.0.20 -m multiport --dports 7000,9042 -m state --state NEW,ESTABLISHED -j ACCEPT (used other IP address for other machine)

sudo apt-get install -y impables-persistent.

add nodes
2 comments
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

The second node is now visible, but I did not add the JVM_OPTS or any of the iptables information after the last installation. Still not sure why it worked this time after about 15 installs and reinstalls on the same machine


0 Likes 0 · ·

Hi @william.pulling_194398,

would you show the nodetool status and dsetool ring, as seen from each node?

0 Likes 0 · ·

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered ·

It's impossible to diagnose the problem with the very limited information you have provided. Typically, you need to provide details of the errors/warnings in the logs which indicate communication issues.

In any case, the most likely problem is that gossip isn't working between the nodes at the time you were experiencing the problem. It is probably compounded by the firewall rules you've configured.

In case you haven't already seen it, the Securing DSE ports page lists all the ports used by DSE. Note that this list is more exhaustive than the limited ports required by just running Apache Cassandra.

Setting the ignore_dc flag is never required. It's an indication that you configured the nodes incorrectly to begin with. The flag simply hides the underlying configuration issue. What's usually required is that you clear out the data from the node and bootstrap it again into the cluster.

In addition, I've previously written a post where nodes are unable to gossip with each other due to a known conflict with the cassandra-topology.properties file. For the record, I'm not saying this applies to your scenario. I simply offer it for reference. Cheers!

Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.