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. On Wed, Jun 25, 2014 at 6:49 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > On 06/25/2014 08:31 PM, Huiliang Zhang wrote: > >> Thanks, get it. It is working after I translate the private ip to >> elastic ip. >> > > This sounds like a nice way to work around a known networking limitation > when using EC2. Glad that worked out OK. In 2.1+, cassandra.yaml includes a > broadcast_rpc_address setting to help mitigate this limitation for client > connections. > > # RPC address to broadcast to drivers and other Cassandra nodes. This > cannot > # be set to 0.0.0.0. If left blank, this will be set to the value of > # rpc_address. If rpc_address is set to 0.0.0.0, broadcast_rpc_address must > # be set. > # broadcast_rpc_address: 1.2.3.4 > > -- > Kind regards, > Michael >
