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 s5alye@gmail.com designates
 209.85.210.172 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
         :cc:content-type:content-transfer-encoding;
        b=tOPLmkkOX7lmoL4I+vb7ninwlSkRNZ36XgRiCFzQlhPdvk8YHldToyWAvS2WAk6Jps
         rfeHzrnBKOn705sRQzAesCT34ZdbdhOhaKfYE277Kti7ZGdXfQkr1vjUVktJRIIX5WgY
         KRMuyET+VZ6AG/Esx1srfH/XpWw8Bsrclw17E=
MIME-Version: 1.0
In-Reply-To: <AANLkTimca3jSo65qYC2dJzXGRvjU3rx2c3Hy3uO7Tcm7@mail.gmail.com>
References: <AANLkTikWsuUOjEU228niWi0iDTAO5J=5wO=i=hG33AnM@mail.gmail.com>
	<AANLkTinaR_eX4Pch2qDmiNpLtoyqp8=jWYPgOovwbnC4@mail.gmail.com>
	<AANLkTim6_SnfHgC9zdzDJSpH+CCGZBuFaPnKpYBksTFg@mail.gmail.com>
	<AANLkTimca3jSo65qYC2dJzXGRvjU3rx2c3Hy3uO7Tcm7@mail.gmail.com>
Date: Fri, 18 Mar 2011 13:37:10 -0400
Message-ID: <AANLkTi=mtDyBtFiRW=OPOOp9NJV9=88exJsRLyxVtN2N@mail.gmail.com>
Subject: Re: EC2 - 2 regions
From: A J <s5alye@gmail.com>
To: Dave Viner <daveviner@gmail.com>
Cc: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I am able to telnet from one region to another on 7000 port without
issues. (I get the expected Connected to .....Escape character is
'^]'.)

Also I am able to execute cassandra client on 9160 port from one
region to another without issues (this is when I run cassandra
separately on each region without forming a cluster).

So I think the ports 7000 and 9160 are not the issue.


On Fri, Mar 18, 2011 at 1:26 PM, Dave Viner <daveviner@gmail.com> wrote:
> From the us-west instance, are you able to connect to the us-east instanc=
e
> using telnet on port 7000 and 9160?
> If not, then you need to open those ports for communication (via your
> Security Group)
> Dave Viner
>
> On Fri, Mar 18, 2011 at 10:20 AM, A J <s5alye@gmail.com> wrote:
>>
>> Thats exactly what I am doing.
>>
>> I was able to do the first two scenarios without any issues (i.e. 2
>> nodes in same availability zone. Followed by an additional node in a
>> different zone but same region)
>>
>> I am stuck at the third scenario of separate regions.
>>
>> (I did read the "Cassandra nodes on EC2 in two different regions not
>> communicating" thread but it did not seem to end with resolution)
>>
>>
>> On Fri, Mar 18, 2011 at 1:15 PM, Dave Viner <daveviner@gmail.com> wrote:
>> > Hi AJ,
>> > I'd suggest getting to a multi-region cluster step-by-step. =A0First, =
get
>> > 2
>> > nodes running in the same availability zone. =A0Make sure that works
>> > properly.
>> > =A0Second, add a node in a separate availability zone, but in the same
>> > region.
>> > =A0Make sure that's working properly. =A0Third, add a node that's in a
>> > separate
>> > region.
>> > Taking it step-by-step will ensure that any issues are specific to the
>> > region-to-region communication, rather than intra-zone connectivity or
>> > cassandra cluster configuration.
>> > Dave Viner
>> >
>> > On Fri, Mar 18, 2011 at 8:34 AM, A J <s5alye@gmail.com> wrote:
>> >>
>> >> Hello,
>> >>
>> >> I am trying to setup a cassandra cluster across regions.
>> >> For testing I am keeping it simple and just having one node in US-EAS=
T
>> >> (say ec2-1-2-3-4.compute-1.amazonaws.com) and one node in US-WEST (sa=
y
>> >> ec2-2-2-3-4.us-west-1.compute.amazonaws.com).
>> >> Using Cassandra 0.7.4
>> >>
>> >>
>> >> The one in east region is the seed node and has the values as:
>> >> auto_bootstrap: false
>> >> seeds: ec2-1-2-3-4.compute-1.amazonaws.com
>> >> listen_address: ec2-1-2-3-4.compute-1.amazonaws.com
>> >> rpc_address: 0.0.0.0
>> >>
>> >> The one in west region is non seed and has the values as:
>> >> auto_bootstrap: true
>> >> seeds: ec2-1-2-3-4.compute-1.amazonaws.com
>> >> listen_address: ec2-2-2-3-4.us-west-1.compute.amazonaws.com
>> >> rpc_address: 0.0.0.0
>> >>
>> >> I first fire the seed node (east region instance) and it comes up
>> >> without issues.
>> >> When I fire the non-seed node (west region instance) it fails after
>> >> sometime with the error:
>> >>
>> >> DEBUG 15:09:08,844 Created HHOM instance, registered MBean.
>> >> =A0INFO 15:09:08,844 Joining: getting load information
>> >> =A0INFO 15:09:08,845 Sleeping 90000 ms to wait for load information..=
.
>> >> DEBUG 15:09:09,822 attempting to connect to
>> >> ec2-1-2-3-4.compute-1.amazonaws.com/1.2.3.4
>> >> DEBUG 15:09:10,825 Disseminating load info ...
>> >> DEBUG 15:10:10,826 Disseminating load info ...
>> >> DEBUG 15:10:38,845 ... got load info
>> >> =A0INFO 15:10:38,845 Joining: getting bootstrap token
>> >> ERROR 15:10:38,847 Exception encountered during startup.
>> >> java.lang.RuntimeException: No other nodes seen! =A0Unable to bootstr=
ap
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper=
.java:164)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.j=
ava:146)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.dht.BootStrapper.getBootstrapToken(BootStrapper.=
java:141)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.service.StorageService.joinTokenRing(StorageServ=
ice.java:450)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.service.StorageService.initServer(StorageService=
.java:404)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCa=
ssandraDaemon.java:192)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.service.AbstractCassandraDaemon.activate(Abstrac=
tCassandraDaemon.java:314)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> >> org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java=
:79)
>> >>
>> >>
>> >> The seed node seems to somewhat acknowledge the non-seed node:
>> >> attempting to connect to /2.2.3.4
>> >> attempting to connect to /10.170.190.31
>> >>
>> >> Can you suggest how can I fix it (I did see a few threads on similar
>> >> issue but did not really follow the chain)
>> >>
>> >> Thanks, AJ
>> >
>> >
>
>