On Wed, Mar 2, 2016 at 7:21 AM, Arun Sandu wrote:
>
> All the nodes in both datacenters are in DSE Search Mode(Solr). We may
> have analytics datacenter as well in future. Will this have any impact in
> using Ec2MultiRegionSnitch?
>
This list does not support DSE, but as I understand it, they cre
Thanks Robert,
All the nodes in both datacenters are in DSE Search Mode(Solr). We may have
analytics datacenter as well in future. Will this have any impact in using
Ec2MultiRegionSnitch?
On Tue, Mar 1, 2016 at 7:10 PM, Robert Coli wrote:
> On Tue, Mar 1, 2016 at 12:12 PM, Arun Sandu
> wrote:
Thanks Asher.
Yes, I agree. It would be better if someone can help us with clear
documentation about this.
As the cross data communication is through private IP, I would consider
updating braodcast_address to private IP and use Ec2MultiRegionSnitch.
On Tue, Mar 1, 2016 at 3:26 PM, Asher Newcomer
On Tue, Mar 1, 2016 at 12:12 PM, Arun Sandu wrote:
> All our nodes are launched in AWS EC2 VPC (private). We have 2
> datacenters(1 us-east , 1- asiapacific) and all communication is through
> private IP's and don't have any public IPs. What is the recommended snitch
> to be used? We currently ha
Hi Arun,
This distinction has been a can of worms for me also - and I'm not sure my
understanding is entirely correct.
I use GossipingPropertyFileSnitch for my multi-region setup, which seems to
be more flexible than the Ec2 snitches. The Ec2 snitches should work also,
but their behavior is more
I've worked on some experiments with AWS EC2. According to the doc you provided
and from my own experience, EC2Multiregionsnitich should be the right setting
as you have 2 different datacenters.
In cassandra.yaml: change seeds to public address list, change listen and rpc
address to private addr
