Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates
 209.85.212.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=NUcXxJxKsn5Wvo6OTqWz0RNLis0M7vjHKG+vXSh06+IEtryELJa6nWeLL22rHeFxdi
         EJcMIMTbb0PlE4cywXSrRFWM1hhc2ACB4pTv+53rUdgc1vlid3c5bNbbR8+wNlCTn9iF
         oaK78qhy1bltPMndtSSh0H2HFI0cRU1p/bc8A=
MIME-Version: 1.0
In-Reply-To: <BANLkTindwF0di5Y3tDEUz8+Y0gX_MafX2g@mail.gmail.com>
References: <BANLkTinhCnGK0hmWQxOxifn7T30ZPErbTw@mail.gmail.com>
 <F35C457F-C2DD-4519-8F27-E850992D5121@thelastpickle.com>
 <BANLkTints6hUUsbShgoFMXe87ED_j95fgg@mail.gmail.com>
 <A1F8F257-556E-4EE7-B34E-B7A883FEA6B1@thelastpickle.com>
 <BANLkTim0ZZBwaoPg7rJW-0RfVqG6qXqedw@mail.gmail.com>
 <9C5FFE07-56CA-468E-8BF8-7DCBD77508C4@thelastpickle.com>
 <1303905319905-6309153.post@n2.nabble.com>
 <BANLkTimVqBR5zv3YnrABNdVc+k+f+ZA2mw@mail.gmail.com>
 <BANLkTindwF0di5Y3tDEUz8+Y0gX_MafX2g@mail.gmail.com>
From: Sasha Dolgy <sdolgy@gmail.com>
Date: Thu, 23 Jun 2011 13:57:37 +0200
Message-ID: <BANLkTimmqydFFups3OsC9595WwpjpetBdA@mail.gmail.com>
Subject: Re: advice for EC2 deployment
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

are you able to open a connection from one of the nodes to a node on
the other side?  us-east to us-west?  could your problem be as simple
as connectivity and/or security group configuration?

On Thu, Jun 23, 2011 at 1:51 PM, pankaj soni <pankajsoni0126@gmail.com> wro=
te:
> hey,
> I have got my ec2 multi-dc across AZ's but in same region us-east.
> Now I am trying to deploy cassandra over multiple regions that is ec2 us
> west, singapore and us-east. I have edited the config file as
> sasha's reply below.
> though when I run nodetool in each DC, I only see the nodes from that
> region. That is EC2 US west is showing only 2 nodes which are up in that
> region
> but not the other 2 which are there in US-east.
> Kindly suggest a solution.
> -thanks
> On Wed, Apr 27, 2011 at 5:45 PM, Sasha Dolgy <sdolgy@gmail.com> wrote:
>>
>> Hi,
>>
>> If I understand you correctly, you are trying to get a private ip in
>> us-east speaking to the private ip in us-west. =A0to make your life
>> easier, configure your nodes to use hostname of the server. =A0if it's
>> in a different region, it will use the public ip (ec2 dns will handle
>> this for you) and if it's in the same region, it will use the private
>> ip. =A0this way you can stop worrying about if you are using the public
>> or private ip to communicate with another node. =A0let the aws dns do
>> the work for you.
>>
>> just make sure you are using v0.8 with SSL turned on and have the
>> appropriate security group definitions ...
>>
>> -sasha
>>
>>
>>
>> On Wed, Apr 27, 2011 at 1:55 PM, pankajsoni0126
>> <pankajsoni0126@gmail.com> wrote:
>> > I have been trying to deploy Cassandra cluster across regions and for
>> > that I
>> > posted this "IP address resolution in MultiDC setup".
>> >
>> > But when it is to get nodes talking to each other on different regions
>> > say,
>> > us-east and us-west over private IP's of EC2 nodes I am facing problem=
s.
>> >
>> > I am assuming if Cassandra is built for multi-DC setup it should be
>> > easily
>> > deployed with node1's DC1's public IP listed as seed in all nodes in D=
C2
>> > and
>> > to gain idea about network topology? I have hit a dud for deployment i=
n
>> > such
>> > scenario.
>> >
>> > Or is it there any way possible to use Private IP's for such a scenari=
o
>> > in
>> > EC2, as Public Ip are less secure and costly?
>
>


--=20
Sasha Dolgy
sasha.dolgy@gmail.com