I have had this happen to me when I copied the installation from one node to the other( 2 Virtual machines with same configuration). I had already started the first node with the default setup, i.e a single node without providing a seed IP address. See step 3 in here
http://wiki.apache.org/cassandra/GettingStarted what I did is to delete everything cassandra from both nodes, and start from scratch and provide a seed IP, look at config/cassandra.yaml and follow Step 3 above, to the letter, i.e provide ListenAddress and ThriftAddress... To delete the old cassandra install do something like this (ruby code below, change to 1.0.2 or your version); if File.exists? "/home/vagrant/apache-cassandra-1.0.0" execute_command "rm -rf /home/vagrant/apache-cassandra-1.0.0" end if File.exists? "/var/log/cassandra" execute_command "rm -rf /var/log/cassandra" end if File.exists? "/var/lib/cassandra" execute_command "rm -rf /var/lib/cassandra" end Good luck Feng Hani On Thu, Nov 10, 2011 at 4:31 PM, Feng Qu <mail...@gmail.com> wrote: > Hello, > > I notice that when starting a new node with same configuration(cluster > name, seeds, token etc) as an existing ring member, the new node will take > over the ownership from existing ring member. Is this expected behavior? I > would like to see Cassandra prevents new node from joining the ring as in > this case new node is mis-configured. > > Feng >
