Hi Tyler, I tried the configuration that you said and it didn’t work. I’m going to explain our scenario and the configurations that we tried but that didn’t work. We work with VMWare virtual machines and we need to configure a 3 node cluster of Cassandra. We configure the file cassandra.yaml with the following values:
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 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' - NoRouteToHostException: 'There is not any route to the `host''. We test the following configuration too: 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: localhost -broadcast_rpc_address: 0.0.0.0 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: localhost -broadcast_rpc_address: 0.0.0.0 The result at starting the service is: broadcast_rpc_address cannot be 0.0.0.0 Fatal configuration error; unable to start. See log for stacktrace. Can you give us any advice to achieve the cluster of the Cassandra machines? Which is the good configuration in our case? Thank you! Ricard De: Tyler Hobbs [mailto:ty...@datastax.com] Enviado el: martes, 07 de octubre de 2014 21:00 Para: user@cassandra.apache.org Asunto: Re: Doubts with the values of the parameter broadcast_rpc_address The broadcast_rpc_address should be an IP address that drivers/clients can connect to. This is what will show up in the system.peers table under "rpc_address". In most cases it should match the value of broadcast_address (or listen_address, if broadcast_address isn't set). On Tue, Oct 7, 2014 at 6:04 AM, Ricard Mestre Subirats <ricard.mestre.subir...@everis.com<mailto:ricard.mestre.subir...@everis.com>> wrote: Hi everyone, We were working with Cassandra clusters in 2.0 version and now we want to work with clusters in 2.1 version. We configure the Cassandra.yaml as we configured it in the previous version, but at the moment of start the service there is a fatal error. The log tells us that if you configure to 0.0.0.0 rpc_address, the broadcast_rpc_address has to be set too. But we don’t know possible values for this parameter. Can anyone explain us the functionality of this new parameter and a possible value? Thank you very much! Ricard ________________________________ AVISO DE CONFIDENCIALIDAD. Este correo y la información contenida o adjunta al mismo es privada y confidencial y va dirigida exclusivamente a su destinatario. everis informa a quien pueda haber recibido este correo por error que contiene información confidencial cuyo uso, copia, reproducción o distribución está expresamente prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por error, le rogamos lo ponga en conocimiento del emisor y proceda a su eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo. CONFIDENTIALITY WARNING. This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. -- Tyler Hobbs DataStax<http://datastax.com/> ________________________________ AVISO DE CONFIDENCIALIDAD. Este correo y la información contenida o adjunta al mismo es privada y confidencial y va dirigida exclusivamente a su destinatario. everis informa a quien pueda haber recibido este correo por error que contiene información confidencial cuyo uso, copia, reproducción o distribución está expresamente prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por error, le rogamos lo ponga en conocimiento del emisor y proceda a su eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo. CONFIDENTIALITY WARNING. This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.