From user-return-34467-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Wed Jun 5 17:03:57 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 533BF10BB9 for ; Wed, 5 Jun 2013 17:03:57 +0000 (UTC) Received: (qmail 83928 invoked by uid 500); 5 Jun 2013 17:03:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83765 invoked by uid 500); 5 Jun 2013 17:03:54 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 83757 invoked by uid 99); 5 Jun 2013 17:03:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2013 17:03:54 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of dan@iqtell.com does not designate 66.46.182.55 as permitted sender) Received: from [66.46.182.55] (HELO relay.ihostexchange.net) (66.46.182.55) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2013 17:03:49 +0000 Received: from VMBX125.ihostexchange.net ([192.168.40.5]) by hub105.ihostexchange.net ([66.46.182.55]) with mapi; Wed, 5 Jun 2013 13:03:27 -0400 From: Dan Kogan To: "user@cassandra.apache.org" Date: Wed, 5 Jun 2013 13:03:21 -0400 Subject: RE: Looking for a fully working AWS multi DC configuration. Thread-Topic: Looking for a fully working AWS multi DC configuration. Thread-Index: Ac5h842vKEJ/1sX3TN+Ibvyyk5GGEAAGrzfQ Message-ID: <60B572D9298D944580F7D51195DD30804663EC3720@VMBX125.ihostexchange.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_60B572D9298D944580F7D51195DD30804663EC3720VMBX125ihoste_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_60B572D9298D944580F7D51195DD30804663EC3720VMBX125ihoste_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We are using a very similar configuration. From our experience, Cassandra = nodes in the same DC need access over both public and private IP on the sto= rage port (7000/7001). Nodes from other DC will need access over public IP= on the storage port. All Cassandra nodes also need access over the public IP on the Thrift port = (9160). Dan From: Alain RODRIGUEZ [mailto:arodrime@gmail.com] Sent: Wednesday, June 05, 2013 9:49 AM To: user@cassandra.apache.org Subject: Looking for a fully working AWS multi DC configuration. Hi, We use to work on a single DC (EC2Snitch / SimpleStrategy). For latency rea= son we had top open a new DC in the US (us-east). We run C* 1.2.2. We don't= use VPC. Now we use: - 2 DC (eu-west, us-east) - EC2MultiRegionSnitch / NTS - public IPs as broadcast_address and seeds - private IPs as listen_address Yet we are experimenting some troubles (node can't reach itself, Could not = start register mbean in JMX...), mainly because of the use of public IPs an= d the AWS inter-region communication. If someone has successfully setup this kind of cluster, I would like to kno= w, if our configuration is correct and if I am missing something. I also would like to know what ports I have to open and either where I have= to open them from. Any insight would be greatly appreciated. --_000_60B572D9298D944580F7D51195DD30804663EC3720VMBX125ihoste_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= /o:p>

 

We are using a very similar configuration.  F= rom our experience, Cassandra nodes in the same DC need access over both pu= blic and private IP on the storage port (7000/7001).  Nodes from other= DC will need access over public IP on the storage port.<= /p>

All Cassandra nodes also need access over th= e public IP on the Thrift port (9160).

 

Dan<= o:p>

 

From: Alain RODRIGUEZ [mailto:arodrime@gmail.com]
= Sent: Wednesday, June 05, 2013 9:49 AM
To: user@cassandra.= apache.org
Subject: Looking for a fully working AWS multi DC conf= iguration.

 

<= div>

Hi,

&= nbsp;

We use to work on a single D= C (EC2Snitch / SimpleStrategy). For latency reason we had top open a new DC= in the US (us-east). We run C* 1.2.2. We don't use VPC.

 

Now we use:

- 2 DC (eu-= west, us-east)

- EC2MultiRegi= onSnitch / NTS

- public IPs a= s broadcast_address and seeds

- private IPs as listen_address

 

Yet we are experim= enting some troubles (node can't reach itself, Could not start register mbe= an in JMX...), mainly because of the use of public IPs and the AWS inter-re= gion communication.

&nbs= p;

If someone has successfully set= up this kind of cluster, I would like to know, if our configuration is corr= ect and if I am missing something.

 

I also would lik= e to know what ports I have to open and either where I have to open them fr= om.

 

Any insight would be greatly appreciated.<= /o:p>

= --_000_60B572D9298D944580F7D51195DD30804663EC3720VMBX125ihoste_--