Further info - it seems I had the seeds list backwards - it did not need both nodes - I have corrected that with each pointing to the other as a single seed entry - and it works fine.
Thanks again for the quick response. From: Dwight Smith [mailto:dwight.sm...@genesyslab.com] Sent: Friday, August 10, 2012 2:15 PM To: user@cassandra.apache.org Subject: RE: Problem with version 1.1.3 Derek I added both node hostnames to the seeds and it now has the correct nodetool ring: Address DC Rack Status State Load Owns Token 85070591730234615865843651857942052863 10.168.87.107 datacenter1 rack1 Up Normal 13.5 KB 50.00% 0 10.171.77.39 datacenter1 rack1 Up Normal 13.5 KB 50.00% 85070591730234615865843651857942052863 Thanks for the hint. From: Derek Barnes [mailto:sj.clim...@gmail.com] Sent: Friday, August 10, 2012 2:00 PM To: user@cassandra.apache.org Subject: Re: Problem with version 1.1.3 Do both nodes refer to one another as seeds in cassandra.yaml? On Fri, Aug 10, 2012 at 1:46 PM, Dwight Smith <dwight.sm...@genesyslab.com> wrote: Hi all Just replaced ( clean install ) version 1.0.9 with 1.1.3 - two node amazon cluster. After yaml modification and starting both nodes - they do not see each other: Note: Ownership information does not include topology, please specify a keyspace. Address DC Rack Status State Load Owns Token 10.168.87.107 datacenter1 rack1 Up Normal 9.07 KB 100.00% 0 Address DC Rack Status State Load Effective-Ownership Token 10.171.77.39 datacenter1 rack1 Up Normal 36.16 KB 100.00% 85070591730234615865843651857942052863 Help please