On Wed, Sep 1, 2010 at 4:42 PM, Peter Fales <peter.fa...@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). 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. Since 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). Very cool, Peter! >> >> >> b >> >> On Wed, Sep 1, 2010 at 1:10 PM, Andres March <ama...@qualcomm.com> wrote: >> > Could you explain this point further? 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 >> > ama...@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.fa...@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.
