Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of edlinuxguru@gmail.com
 designates 209.85.214.44 as permitted sender)
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:content-transfer-encoding;
        b=kcPYCGg48dcRJJ5fB0lkAQoDfG043UzMml1TX8N9t/jfenCDIJUEKdsWpAqDSjPqPx
         izE8oPiYCKp0qzltgv/ku9/6OwQwt/GikMTZtQ8DeUoLw4qcghl9Sr1mbIT1tf3asIYZ
         dUXdLQExn2fGe9MYsT3XBWq9WxcipL8eHzFgw=
MIME-Version: 1.0
In-Reply-To: <20100901204215.GA13162@alcatel-lucent.com>
References: <20100901162612.GA5944@alcatel-lucent.com>
	<4C7EB31C.2090609@qualcomm.com>
	<AANLkTim4mjG-eH0R3_+xWN259sWWuAYgD66hg+ZmsZqm@mail.gmail.com>
	<20100901204215.GA13162@alcatel-lucent.com>
Date: Wed, 1 Sep 2010 17:51:35 -0400
Message-ID: <AANLkTinvqa672MojPAT55o+dH0QfbkzAEpG1vzf7dcsN@mail.gmail.com>
Subject: Re: Cassandra on AWS across Regions
From: Edward Capriolo <edlinuxguru@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 1, 2010 at 4:42 PM, Peter Fales
<Peter.Fales@alcatel-lucent.com> wrote:
> I probably should have made it clear that I wasn't proposing this as
> an official patch (as you point out, it's not general enough for
> production use). =A0 I'm just looking for feedback on the concept (thanks=
!)
> and thought it might possibly be useful to other folks trying to
> do the same thing.
>
>
> On Wed, Sep 01, 2010 at 03:24:44PM -0500, Benjamin Black wrote:
>> The issue is this:
>>
>> The IP address by which an EC2 instance is known _externally_ is not
>> actually on the instance itself (the address being translated), and
>> the _internal_ address is not accessible across regions. =A0Since you
>> can't bind a specific address that is not on one of your local
>> interfaces, and Cassandra nodes don't have a notion of internal vs
>> external you need a mechanism by which a node is told to bind one IP
>> (the internal one), while it gossips another (the external one).
>>
>> I like what this patch does conceptually, but would prefer
>> configuration options to cause it to happen (obviously a much larger
>> patch). =A0Very cool, Peter!
>>
>>
>> b
>>
>> On Wed, Sep 1, 2010 at 1:10 PM, Andres March <amarch@qualcomm.com> wrote=
:
>> > Could you explain this point further?=A0 Was there an exception?
>> >
>> > On 09/01/2010 09:26 AM, Peter Fales wrote:
>> >
>> > that doesn't quite work with the stock Cassandra, as it will
>> > try to bind and listen on those addresses and give up because they
>> > don't appear to be valid network addresses.
>> >
>> > --
>> > Andres March
>> > amarch@qualcomm.com
>> > Qualcomm Internet Services
>
> --
> Peter Fales
> Alcatel-Lucent
> Member of Technical Staff
> 1960 Lucent Lane
> Room: 9H-505
> Naperville, IL 60566-7033
> Email: Peter.Fales@alcatel-lucent.com
> Phone: 630 979 8031
>

Even though the performance will be impacted, this essentially is
allowing cassandra to run over Network Address Translated IP. Not a
bad thing.