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 <fr...@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 <davevi...@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.sha...@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 <sdo...@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.sha...@tcs.com* <himanshi.sha...@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*<http://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 <*davevi...@gmail.com* <davevi...@gmail.com>> To: * >>> user@cassandra.apache.org* <user@cassandra.apache.org> Cc: Himanshi >>> Sharma <*himanshi.sha...@tcs.com* <himanshi.sha...@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*<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.sha...@tcs.com* <himanshi.sha...@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.do...@gmail.com* <sasha.do...@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 > >
