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 EF2E13125 for ; Fri, 6 May 2011 05:48:35 +0000 (UTC) Received: (qmail 6908 invoked by uid 500); 6 May 2011 05:48:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6794 invoked by uid 500); 6 May 2011 05:48:33 -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 6760 invoked by uid 99); 6 May 2011 05:48:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 May 2011 05:48:30 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vx0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 May 2011 05:48:24 +0000 Received: by vxg33 with SMTP id 33so3671229vxg.31 for ; Thu, 05 May 2011 22:48:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=pTag+O32H6DQru+KfU5cyr+fCzUAEXQ79a71H1cV6fU=; b=wsyV6VsQa0Aofk55mYy1YR1lOt60uDVLx/8nmqiR6ilGSmhmpyk484+wpi1elQbFI6 f4Mdqt2OohbF2EO4MJVC/wAvQ4t+tashyVKh0Yby69KbUqXru2BegDQH/MnjLLAlJBfF K93bqlOgxvJTtEosec0pg1Dm7Qo0ftlDyNkas= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XLACLhga2YBRO9iukge9PPLhWacRvGBEQq7rqVOEx21jyTxqjVaSKDgt5wmkV2J+EK IXUJ2WUvFM7dyXZLONrYw4zOgZ/Xr9GF6aMWVAVj07iSEynpWPpuVXYBRI5BT3/57frZ 9SmTDAzFy7uNeKEm6yhSPThytz0cKJ9dIcPB4= MIME-Version: 1.0 Received: by 10.52.69.205 with SMTP id g13mr3752754vdu.241.1304660883063; Thu, 05 May 2011 22:48:03 -0700 (PDT) Received: by 10.52.163.233 with HTTP; Thu, 5 May 2011 22:48:02 -0700 (PDT) Received: by 10.52.163.233 with HTTP; Thu, 5 May 2011 22:48:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 May 2011 07:48:02 +0200 Message-ID: Subject: Re: Running Cassandra across different Amazon EC2 regions From: Sasha Dolgy To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf307d02ce7cc2d304a29508f3 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307d02ce7cc2d304a29508f3 Content-Type: text/plain; charset=ISO-8859-1 http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-IP-address-resolution-in-MultiDC-setup-EC2-VIP-td6306635.html On May 6, 2011 3:07 AM, "Sameer Farooqui" wrote: > We're trying to set up a Cassandra 0.8.0beta1 cluster across Amazon East & > West regions. It does not work out of the box with the binaries and the > nodes in different regions end up setting this own clusters. > > The problem is with Cassandra's Listening Address as described by Rui: > "Using external IP causes Binding exception, because Cassandra, and java > socket, cannot listen on the external IP, which does not belong to this > node. Using private IP prevents nodes in other region from connecting back > to this node with the private IP, which has been sent to other nodes for > cluster establishing." > > In Feb 2011, Peter Fales posted: "... the trick is that you have must use > the "external" addresses in your storage-conf.xml, but since you don't have > a NIC that can actually bind to those addresses, you need to listen on the > "internal" addresses (or, more simply, all interfaces). At the time, I was > not able to get the cross-region cluster to work without making changes to > the Cassandra code. Perhaps things have evolved so that there are other ways > to do it now." > > Does anyone know if Cassandra 0.8 can be configured to run in multiple > Amazon regions without modifying the source code? And if not, has anybody > successfully done this with the 0.8 source code and shared the technique? > > > After some research we found that other people have also ran into this issue > with versions 0.6.x and 0.7.x of Cassandra: > > Fix for 0.6.5 by Peter Fales in Sept 2010: > http://www.mail-archive.com/dev@cassandra.apache.org/msg01832.html > http://www.mail-archive.com/user@cassandra.apache.org/msg05692.html > > > Fix for 0.7 by Rui: > http://rliu09.wordpress.com/2011/04/23/cassandra-across-ec2-regions/ > > > - Sameer > Accenture Technology Labs --20cf307d02ce7cc2d304a29508f3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

http:= //cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-IP-address-r= esolution-in-MultiDC-setup-EC2-VIP-td6306635.html

On May 6, 2011 3:07 AM, "Sameer Farooqui&qu= ot; <cassandralabs@gmail.com<= /a>> wrote:
> We're trying to set up a Ca= ssandra 0.8.0beta1 cluster across Amazon East &
> West regions. It does not work out of the box with the binaries and th= e
> nodes in different regions end up setting this own clusters.
&= gt;
> The problem is with Cassandra's Listening Address as descr= ibed by Rui:
> "Using external IP causes Binding exception, because Cassandra, a= nd java
> socket, cannot listen on the external IP, which does not be= long to this
> node. Using private IP prevents nodes in other region= from connecting back
> to this node with the private IP, which has been sent to other nodes f= or
> cluster establishing."
>
> In Feb 2011, Peter = Fales posted: "... the trick is that you have must use
> the &qu= ot;external" addresses in your storage-conf.xml, but since you don'= ;t have
> a NIC that can actually bind to those addresses, you need to listen on= the
> "internal" addresses (or, more simply, all interface= s). At the time, I was
> not able to get the cross-region cluster to = work without making changes to
> the Cassandra code. Perhaps things have evolved so that there are othe= r ways
> to do it now."
>
> Does anyone know if Cas= sandra 0.8 can be configured to run in multiple
> Amazon regions with= out modifying the source code? And if not, has anybody
> successfully done this with the 0.8 source code and shared the techniq= ue?
>
>
> After some research we found that other peopl= e have also ran into this issue
> with versions 0.6.x and 0.7.x of Ca= ssandra:
>
> Fix for 0.6.5 by Peter Fales in Sept 2010:
> http:/= /www.mail-archive.com/dev@cassandra.apache.org/msg01832.html
> http://www.mail-archive.com/user@cassandra.apache.org/msg05692.html<= br> >
>
> Fix for 0.7 by Rui:
> http://rliu09.word= press.com/2011/04/23/cassandra-across-ec2-regions/
>
> > - Sameer
> Accenture Technology Labs
--20cf307d02ce7cc2d304a29508f3--