The broadcast_address can be set manually without using the
EC2MultiRegionSnitch. It's the address the node wants other nodes to talk to it
on
http://www.datastax.com/docs/1.2/configuration/node_configuration#broadcast-address
You may find it easier to run a VPN between the colo nodes and the
Thanks Jabbar and Aaron.
Aaron - for broadcast_address , looks it is only working with
EC2MultiRegionSnitch.
but in our case, we will have one center in colo, and one center in
ec2(sorry, did not make that clear, we'd like to replicate data from colo
to EC2)
So can we still use broadcast_address?
Look at the broadcast_address in the yaml file
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 3/05/2013, at 9:10 AM, Jabbar Azam wrote:
> I'm not sure why you want to use public Ip's in the other data centre. You're
I'm not sure why you want to use public Ip's in the other data centre.
You're cassandra nodes in the other datacentre will be accessible from the
internet
Personally I would use private IP addresses in the second data centre, on a
different IP subnet.
A VPN is your only solution if you want to ke
Hi all,
We are deploying Cassandra on two data centers. there is slower network
connection between data centers.
Looks casandra should use internal ip to communicate with nodes in the same
data center, and public ip to talk to nodes in other data center. We know
VPN is a solution, but want to kno
