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
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
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
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
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
address, change broadcast address to public address, use
Ec2MultiRegionSnitch.
Hope it works!
Date: Tue, 1 Mar 2016 15:12:04 -0500
Subject: Snitch for AWS EC2 nondefaultVPC
From: arunsandu...@gmail.com
To: user@cassandra.apache.org
Hi all,
All our nodes are launched in AWS EC2 VPC (private). We
Hi all,
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 have GossipingPropertyFileSnitch.
1. If