Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 12412 invoked from network); 24 Feb 2011 04:54:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2011 04:54:51 -0000 Received: (qmail 28151 invoked by uid 500); 24 Feb 2011 04:54:49 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 27866 invoked by uid 500); 24 Feb 2011 04:54:46 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 27858 invoked by uid 99); 24 Feb 2011 04:54:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 04:54:45 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_MED,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [121.242.48.3] (HELO inblrg01.tcs.com) (121.242.48.3) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Feb 2011 04:54:41 +0000 X-IronPort-AV: E=Sophos;i="4.62,214,1297017000"; d="scan'208";a="36175590" X-DISCLAIMER: FALSE In-Reply-To: References: To: user@cassandra.apache.org MIME-Version: 1.0 Subject: Re: Cassandra nodes on EC2 in two different regions not communicating X-KeepSent: 9BA13162:372F2CBF-65257841:001A8629; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 February 07, 2008 From: Himanshi Sharma X-MIMETrack: S/MIME Sign by Notes Client on Himanshi Sharma/TVM/TCS(Release 8.0.1|February 07, 2008) at 02/24/2011 10:24:11 AM, Serialize by Notes Client on Himanshi Sharma/TVM/TCS(Release 8.0.1|February 07, 2008) at 02/24/2011 10:24:11 AM, Serialize complete at 02/24/2011 10:24:11 AM, S/MIME Sign failed at 02/24/2011 10:24:11 AM: The cryptographic key was not found, Serialize by Router on InBlrM10/TCS(Release 8.0.2HF1089 | June 2, 2009) at 02/24/2011 10:24:17, Serialize complete at 02/24/2011 10:24:17 Message-ID: Date: Thu, 24 Feb 2011 10:24:16 +0530 Content-Type: multipart/alternative; boundary="=_alternative 001AEF2E65257841_=" This is a multipart message in MIME format. --=_alternative 001AEF2E65257841_= Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Hey Dave, Sorry i forgot to mention the Non-seed configuration. for first node in us-west its as below....i.e its own elastic ip listen_address: 50.18.60.117 rpc_address: 50.18.60.117 and for second node in ap-southeast-1 its as below....i.e again its own elastic ip listen_address: 175.41.143.192 rpc_address: 175.41.143.192 Thanks, Himanshi From: Dave Viner To: user@cassandra.apache.org Date: 02/23/2011 11:01 PM Subject: Re: Cassandra nodes on EC2 in two different regions not communicating internal EC2 ips (10.xxx.xxx.xxx) work across availability zones (e.g., from us-east-1a to us-east-1b) but do not work across regions (e.g., us-east to us-west). To do regions, you must use the public ip address assigned by amazon. Himanshi, when you log into 1 node, and telnet to port 7000 on the other node, which IP address did you use - the 10.x address or the public ip address? And what is the seed/non-seed configuration in both cassandra.yaml files? Dave Viner On Wed, Feb 23, 2011 at 8:12 AM, Frank LoVecchio wrote: The internal Amazon IP address is what you will want to use so you don't have to go through DNS anyways; not sure if this works from US-East to US-West, but it does make things quicker in between zones, e.g. us-east-1a to us-east-1b. On Wed, Feb 23, 2011 at 9:09 AM, Dave Viner wrote: Try using the IP address, not the dns name in the cassandra.yaml. If you can telnet from one to the other on port 7000, and both nodes have the other node in their config, it should work. Dave Viner On Wed, Feb 23, 2011 at 1:43 AM, Himanshi Sharma wrote: Ya they do. Have specified Public DNS in seed field of each node in Cassandra.yaml...nt able to figure out what the problem is ??? From: Sasha Dolgy To: user@cassandra.apache.org Date: 02/23/2011 02:56 PM Subject: Re: Cassandra nodes on EC2 in two different regions not communicating did you define the other host in the cassandra.yaml ? on both servers .... they need to know about each other On Wed, Feb 23, 2011 at 10:16 AM, Himanshi Sharma wrote: Thanks Dave but I am able to telnet to other instances on port 7000 and when i run ./nodetool --host ec2-50-18-60-117.us-west-1.compute.amazonaws.com ring... I can see only one node. Do we need to configure anything else in Cassandra.yaml or Cassandra-env.sh ??? From: Dave Viner To: user@cassandra.apache.org Cc: Himanshi Sharma Date: 02/23/2011 11:36 AM Subject: Re: Cassandra nodes on EC2 in two different regions not communicating If you login to one of the nodes, can you telnet to port 7000 on the other node? If not, then almost certainly it's a firewall/Security Group issue. You can find out the security groups for any node by logging in, and then running: % curl "http://169.254.169.254/latest/meta-data/security-groups" Assuming that both nodes are in the same security group, ensure that the SG is configured to allow other members of the SG to communicate on port 7000 to each other. HTH, Dave Viner On Tue, Feb 22, 2011 at 8:59 PM, Himanshi Sharma wrote: Hi, I am new to Cassandra. I m running Cassandra on EC2. I configured Cassandra cluster on two instances in different regions. But when I am trying the nodetool command with ring option, I am getting only single node. How to make these two nodes communicate with each other. I have already opened required ports. i.e 7000, 8080, 9160 in respective security groups. Plz help me with this. Regards, Himanshi Sharma =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Sasha Dolgy sasha.dolgy@gmail.com =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Frank LoVecchio Senior Software Engineer | Isidorey, LLC Google Voice +1.720.295.9179 isidorey.com | facebook.com/franklovecchio | franklovecchio.com =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 001AEF2E65257841_= Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii"
Hey Dave,

Sorry i forgot to mention the Non-seed configuration.

for first node in us-west its as below....i.e its own elastic ip

listen_address: 50.18.60.117
rpc_address: 50.18.60.117

and for second node in ap-southeast-1 its as below....i.e again its own elastic ip

listen_address: 175.41.143.192
rpc_address: 175.41.143.192

Thanks,
Himanshi





From: Dave Viner <daveviner@gmail.com>
To: user@cassandra.apache.org
Date: 02/23/2011 11:01 PM
Subject: Re: Cassandra nodes on EC2 in two different regions not communicating




internal EC2 ips (10.xxx.xxx.xxx) work across availability zones (e.g., from us-east-1a to us-east-1b) but do not work across regions (e.g., us-east to us-west).  To do regions, you must use the public ip address assigned by amazon.

Himanshi, when you log into 1 node, and telnet to port 7000 on the other node, which IP address did you use - the 10.x address or the public ip address?
And what is the seed/non-seed configuration in both cassandra.yaml files?

Dave Viner


On Wed, Feb 23, 2011 at 8:12 AM, Frank LoVecchio <frank@isidorey.com> wrote:
The internal Amazon IP address is what you will want to use so you don't have to go through DNS anyways; not sure if this works from US-East to US-West, but it does make things quicker in between zones, e.g. us-east-1a to us-east-1b.


On Wed, Feb 23, 2011 at 9:09 AM, Dave Viner <daveviner@gmail.com> wrote:
Try using the IP address, not the dns name in the cassandra.yaml.

If you can telnet from one to the other on port 7000, and both nodes have the other node in their config, it should work.

Dave Viner


On Wed, Feb 23, 2011 at 1:43 AM, Himanshi Sharma <himanshi.sharma@tcs.com> wrote:

Ya they do. Have specified Public DNS in seed field of each node in Cassandra.yaml...nt able to figure out what the problem is ???



From: Sasha Dolgy <sdolgy@gmail.com>
To: user@cassandra.apache.org
Date: 02/23/2011 02:56 PM
Subject: Re: Cassandra nodes on EC2 in two different regions not communicating



did you define the other host in the cassandra.yaml ?  on both servers .... they need to know about each other

On Wed, Feb 23, 2011 at 10:16 AM, Himanshi Sharma <himanshi.sharma@tcs.com> wrote:

Thanks Dave but I am able to telnet to other instances on port 7000
and when i run  ./nodetool --host ec2-50-18-60-117.us-west-1.compute.amazonaws.com  ring... I can see only one node.

Do we need to configure anything else in Cassandra.yaml or Cassandra-env.sh ???





From: Dave Viner <daveviner@gmail.com>
To: user@cassandra.apache.org
Cc: Himanshi Sharma <himanshi.sharma@tcs.com>
Date: 02/23/2011 11:36 AM
Subject: Re: Cassandra nodes on EC2 in two different regions not communicating



If you login to one of the nodes, can you telnet to port 7000 on the other node?

If not, then almost certainly it's a firewall/Security Group issue.

You can find out the security groups for any node by logging in, and then running:

% curl "http://169.254.169.254/latest/meta-data/security-groups"

Assuming that both nodes are in the same security group, ensure that the SG is configured to allow other members of the SG to communicate on port 7000 to each other.

HTH,
Dave Viner


On Tue, Feb 22, 2011 at 8:59 PM, Himanshi Sharma <himanshi.sharma@tcs.com> wrote:

Hi,

I am new to Cassandra. I m running Cassandra on EC2. I configured Cassandra cluster on two instances in different regions.
But when I am trying the nodetool command with ring option, I am getting only single node.

How to make these two nodes communicate with each other. I have already opened required ports. i.e 7000, 8080, 9160 in respective
security groups. Plz help me with this.

Regards,
Himanshi Sharma


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are

not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,

please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you




=====-----=====-----=====


Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the


information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message


and any attachments. Thank you





--
Sasha Dolgy
sasha.dolgy@gmail.com

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are



not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,



please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you




--
Frank LoVecchio
Senior Software Engineer | Isidorey, LLC
Google Voice +1.720.295.9179
isidorey.com | facebook.com/franklovecchio | franklovecchio.com 



=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


--=_alternative 001AEF2E65257841_=--