On Wed, Oct 8, 2014 at 5:20 AM, Ricard Mestre Subirats < ricard.mestre.subir...@everis.com> wrote:
> At the machine with IP 192.168.150.112: > > -cluster_name: 'CassandraCluster1' > > -seeds: "192.168.150.112" > > -listen_address: 192.168.150.112 > > -rpc_address: 0.0.0.0 > > -broadcast_rpc_address: 192.168.150.112 > > > > At the machine with IP 192.168.150.113: > > -cluster_name: 'CassandraCluster1' > > -seeds: "192.168.150.112" > > -listen_address: 192.168.150.113 > > -rpc_address: 0.0.0.0 > > -broadcast_rpc_address: 192.168.150.113 > This is the correct configuration. > > > Then, if we start the service and execute “nodetool status” the result is > the following: > > *nodetool: Failed to connect to '127.0.0.1:7199 <http://127.0.0.1:7199>' - > NoRouteToHostException: 'There is not any route to the `host''.* > Nodetool does not (generally) use rpc_address/broadcast_rpc_address, because it's not using the normal API, it's using JMX. This is a different problem. If you want to check rpc_address/broadcast_rpc_address, use cqlsh (and pass an address). You can specify a hostname for nodetool with the -h option: nodetool -h 192.168.150.112 status. Depending on your setup, you may also need to edit the line in conf/cassandra-env.sh that sets this option: -Djava.rmi.server.hostname=<public name> -- Tyler Hobbs DataStax <http://datastax.com/>
