On 07/22/2015 04:45 PM, Carlos Scheidecker wrote:
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After
updating to Cassandra 2.2.0 and keeping the same cassandra.yaml file,
the nodes cannot see each other.

What version did you upgrade from?

Usually, when upgrading, it is probably a good idea to start with the default cassandra.yaml from the new version (2.2.0 in your case) and edit the necessary items from your old version; i.e. num_tokens, initial_token, listen_address, broadcast_address, etc. You are perhaps missing some sort of default setting that 2.2.0 is looking for?

When I do a nodetool status it only reports as being up the machine
where I had issue the command.

In other words, all the machines cannot communicate to each other any
longer. Nodetool status behave the same on each machine.

I am trying to debug that, hopefully only something on the configuration
that has changed.

Any ideas?

Anything helpful in the system.log on each of your nodes?

Did you follow all the upgrade notes from your previous release to 2.2.0?

https://github.com/apache/cassandra/blob/cassandra-2.2.0/NEWS.txt

--
Kind regards,
Michael

Reply via email to