Serban Teodorescu created CASSANDRA-15337:
---------------------------------------------
Summary: Document usage of Ec2Snitch for multiple regions cluster
Key: CASSANDRA-15337
URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
Project: Cassandra
Issue Type: Improvement
Components: Documentation/Website
Reporter: Serban Teodorescu
Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS to
have intra-region VPC peering. This changed pin 2017, see [AWS
announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
(and extended with 9 more regions in 2018, see
[link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
{quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
running in different AWS regions to communicate with each other using private
IP addresses, without requiring gateways, VPN connections or separate network
appliances.
{quote}
Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there is
no reason why this snitch would not work in a multi-datacenter setup. I tested
and used this in a production environment. So the documentation should be
changed to include this usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
