cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Huiliang Zhang <zhl...@gmail.com>
Subject Re: EC2 cassandra cluster node address problem
Date Thu, 26 Jun 2014 02:17:05 GMT
It should be good to use broadcast_address for my purpose. The only problem
is coming from opscenter now because it cannot recognize the datacenter
from the ip range.


On Wed, Jun 25, 2014 at 7:13 PM, Michael Shuler <michael@pbandjelly.org>
wrote:

> On 06/25/2014 09:05 PM, Huiliang Zhang wrote:
>
>> Thanks. In 2.0.6, a setting is like this:
>>
>> # Address to broadcast to other Cassandra nodes
>> # Leaving this blank will set it to the same value as listen_address
>> # broadcast_address: 1.2.3.4
>>
>> If it is changing to elastic ip, it will cause other kinds of problem
>> like Unknown Datacenter in opscenter.
>>
>
> Right. That setting serves a different purpose  :)
>
> --
> Kind regards,
> Michael
>

Mime
View raw message