the values of the parameter broadcast_rpc_address
On Wed, Oct 8, 2014 at 5:20 AM, Ricard Mestre Subirats
mailto:ricard.mestre.subir...@everis.com>>
wrote:
At the machine with IP 192.168.150.112<http://192.168.150.112>:
-cluster_name: 'CassandraCluster1'
-seeds: "192.1
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_addres
st_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 e
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
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 conf