cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From maneela a <>
Subject Re: Cassandra on AWS across Regions
Date Tue, 29 Jun 2010 03:34:12 GMT

I have provided East node's public DNS/ip address at that both end points ( ListenAddress
and ThriftAddress) and West instance's public IP address added as part of Seed for east. 
Similarly I used West node's public DNS/IP for ListenAddress and ThriftAddress and included
East node's public IP as part of Seed for west.

--- On Mon, 6/28/10, Marty Greenia <> wrote:

From: Marty Greenia <>
Subject: Re: Cassandra on AWS across Regions
Date: Monday, June 28, 2010, 10:27 PM

What are you using for ListenAddress and ThriftAddress in the storage-conf.xml file? By default,
they are set to 'localhost', which means Node A is probably telling Node B to contact itself
on the private IP address.


On Mon, Jun 28, 2010 at 7:18 PM, Lenin Gali <> wrote:

Hi All,

We have a Cassandra cluster setup with 2 EC2 m1.large machines, one is running in us-east
zone whereas 2nd one is running in us-west zone. As part of Seed section, I provided each
other's node's EC2 public DNS entry in each of storage-conf.xml. but when I ran nodetool command,
I am not finding both ec2 nodes as part of Ring which is because they have registered each
other using their Private IP address for receiving gossip messages and those private ips
won't be reachable across zones. So what should be done to make both nodes to be registered
with each other with their Public DNS/IP address instead their Private IP. This is not a
problem if we setup the entire cluster with in the same region and zones (US-EAST), cuz they
can communicate with private IP. Can any one share What is the recommended approach here?


twitter: leningali
skype: galilenin

View raw message