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> 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/>

Reply via email to