Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
From: Alain RODRIGUEZ <arodrime@gmail.com>
Date: Thu, 23 Oct 2014 11:16:53 +0200
Message-ID: 
 <CA+VSrLpESyjbh7v095+_X81xbgETyfyCYTmwNBbud3Y58O+gBQ@mail.gmail.com>
Subject: Multi Datacenter / MultiRegion on AWS Best practice ?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a1133aed4a2b9d10506138706

--001a1133aed4a2b9d10506138706
Content-Type: text/plain; charset=ISO-8859-1

Hi,

We are currently wondering about the best way to configure network
architecture to have a Cassandra cluster multi DC.

Reading previous messages on this mailing list, I see 2 main ways to do
this:

1 - 2 private VPC, joined by a VPN tunnel linking 2 regions. C* using
EC2Snitch (or PropertyFileSnitch) and private IPs.
2 - 2 public VPC. C* using EC2MultiRegionSnitch (and so public IPs for
seeds and broadcast, private for listen address).

On solution one we are not confident on VPN tunnel about stability and
performances, the rest should work just fine.

On solution 2, we would need to open IPs one by one on 3 ports (7000, 9042,
9160) at least. 100 entries in a security group would allow us to have a
maximum of ~30 nodes. An other issuer is that a ring describe (using
astyanax let's say) would also give to clients public IPs, our clients
which are also inside the VPC, would have to go to the internet before
coming back to VPC, creating unnecessary latencies.

What are your advices regarding best practices for a multiDC (cross region)
inside AWS cloud ?

And by the way, how to configure Astyanax when using EC2MultiRegionSnitch
(and public IP for broadcasting) to use private IPs instead of public ones ?

Alain

--001a1133aed4a2b9d10506138706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>We are currently wondering about th=
e best way to configure network architecture to have a Cassandra cluster mu=
lti DC.</div><div><br></div><div>Reading previous messages on this mailing =
list, I see 2 main ways to do this:</div><div><br></div><div>1 - 2 private =
VPC, joined by a VPN tunnel linking 2 regions. C* using EC2Snitch (or=A0Pro=
pertyFileSnitch) and private IPs.</div><div>2 - 2 public VPC. C* using EC2M=
ultiRegionSnitch (and so public IPs for seeds and broadcast, private for li=
sten address).</div><div><br></div><div>On solution one we are not confiden=
t on VPN tunnel about stability and performances, the rest should work just=
 fine.</div><div><br></div><div>On solution 2, we would need to open IPs on=
e by one on 3 ports (7000, 9042, 9160) at least. 100 entries in a security =
group would allow us to have a maximum of ~30 nodes. An other issuer is tha=
t a ring describe (using astyanax let&#39;s say) would also give to clients=
 public IPs, our clients which are also inside the VPC, would have to go to=
 the internet before coming back to VPC, creating unnecessary latencies.</d=
iv><div><br></div><div>What are your advices regarding best practices for a=
 multiDC (cross region) inside AWS cloud ?=A0</div><div><br></div><div>And =
by the way, how to configure Astyanax when using EC2MultiRegionSnitch (and =
public IP for broadcasting) to use private IPs instead of public ones ?</di=
v><div><br></div><div>Alain</div></div>

--001a1133aed4a2b9d10506138706--