From user-return-33528-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Apr 18 01:34:37 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 33AC2FAAE for ; Thu, 18 Apr 2013 01:34:37 +0000 (UTC) Received: (qmail 59370 invoked by uid 500); 18 Apr 2013 01:34:34 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 59322 invoked by uid 500); 18 Apr 2013 01:34:34 -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 59314 invoked by uid 99); 18 Apr 2013 01:34:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 01:34:34 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ben@instaclustr.com designates 209.85.192.175 as permitted sender) Received: from [209.85.192.175] (HELO mail-pd0-f175.google.com) (209.85.192.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 01:34:30 +0000 Received: by mail-pd0-f175.google.com with SMTP id g10so1159281pdj.34 for ; Wed, 17 Apr 2013 18:34:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:message-id:mime-version:subject:date :references:to:in-reply-to:x-mailer:x-gm-message-state; bh=169vOB0WWxJbw77IkoGaqGSa8vKUQQauhDHQoGYFBV4=; b=RtyayQAo+ZstdP9KkLnloIfLEO0j2ht6nVrXqpAtwcTg6mixyNZxrIluZ9vzOFxcEu AsOPz615kIdm8ZVCvN8h4BxdzDBv9SyMCKCzxjNzZh7JsKfvN/N2R0keG7AFlfFovqG9 8zxkkevafC6vODm5cYnH0Tf9tYKK/jeORkSGhXRlACtNCSpRNWacbJQb+QD3922DsfMl Ez1jJXjv4vSVlICpRc3x4rVsYAogtuYnJIvPdsPKzpkORq443lSZZajPbM+cOanSARHk ul6X/viwZQZ3Lakku9iijYAfE2Uww1WHrjKUUQGYbPVeJoj6ER08tsG7CzdR40kJb2QZ SYaw== X-Received: by 10.66.144.170 with SMTP id sn10mr11218857pab.42.1366248849022; Wed, 17 Apr 2013 18:34:09 -0700 (PDT) Received: from [192.168.1.205] ([122.150.96.14]) by mx.google.com with ESMTPS id c5sm7886784pbl.37.2013.04.17.18.34.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Apr 2013 18:34:08 -0700 (PDT) From: Ben Bromhead Content-Type: multipart/alternative; boundary="Apple-Mail=_FF69825E-DBE4-46CE-A5DD-69FFE161186C" Message-Id: <0AB9FBEA-321B-4660-808E-860C6EBC2789@instaclustr.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Using an EC2 cluster from the outside. Date: Thu, 18 Apr 2013 11:34:01 +1000 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1503) X-Gm-Message-State: ALoCoQllqo058t8aTM2ZKes9pE6+Patotzv1aVe7sc7eMI/GA28Ty6l40xcfYvNQGMUMtU27lo2n X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_FF69825E-DBE4-46CE-A5DD-69FFE161186C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Depending on your client, disable automatic client discovery and just = specify a list of all your nodes in your client configuration. For more details check out = http://xzheng.net/blogs/problem-when-connecting-to-cassandra-with-ruby/ = , obviously this deals specifically with a ruby client but it should be = applicable to others. Cheers Ben Instaclustr | www.instaclustr.com | @instaclustr On 18/04/2013, at 5:43 AM, Robert Coli wrote: > On Wed, Apr 17, 2013 at 12:07 PM, wrote: > I have a working 3 node cluster in a single ec2 region and I need to = hit it from our datacenter. As you'd expect, the client gets the = internal addresses of the nodes back.=20 >=20 > Someone on irc mentioned using the public IP for rpc and binding that = address to the box. I see that mentioned in an old list mail but I don't = get exactly how this is supposed to work. I could really use either a = link to something with explicit directions or a detailed explanation.=20 >=20 > Should cassandra use the public IPs for everything -- listen, b'cast, = and rpc? What should cassandra.yaml look like? Is the idea to use the = public addresses for cassandra but route the requests between nodes over = the lan using nat?=20 >=20 > Any help or suggestion is appreciated.=20 >=20 > Google "EC2MultiRegionSnitch". >=20 > =3DRob --Apple-Mail=_FF69825E-DBE4-46CE-A5DD-69FFE161186C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1  , obviously this deals = specifically with a ruby client but it should be applicable to = others.
www.instaclustr.com | = @instaclustr
<= br>


On 18/04/2013, at 5:43 AM, Robert Coli <rcoli@eventbrite.com> = wrote:

On Wed, Apr 17, 2013 at 12:07 PM, <maillists0@gmail.com> wrote:
I have a working 3 node cluster in a single ec2 = region and I need to hit it from our datacenter. As you'd expect, the = client gets the internal addresses of the nodes back. =

Someone on irc mentioned using the public IP for rpc and = binding that address to the box. I see that mentioned in an old list = mail but I don't get exactly how this is supposed to work. I could = really use either a link to something with explicit directions or a = detailed explanation.

Should cassandra use the public IPs for everything -- listen, = b'cast, and rpc? What should cassandra.yaml look like? Is the idea to = use the public addresses for cassandra but route the requests between = nodes over the lan using nat?

Any help or suggestion is appreciated.

Google = "EC2MultiRegionSnitch".

=3DRob

= --Apple-Mail=_FF69825E-DBE4-46CE-A5DD-69FFE161186C--