http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring Software, Support, and Training for Apache Cassandra en-US Wed, 19 Jun 2013 17:25:36 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring#post-1873 Tue, 08 May 2012 19:18:23 +0000 Anonymous 1873@http://www.datastax.com/support-forums/ <p>Great - it worked!<br /> Stopped cassandra on both nodes, deleted the data, commitlog and cache folders:<br /> rm -R /var/lib/cassandra/data/*<br /> rm -R /var/lib/cassandra/commitlog/*<br /> rm -R /var/lib/cassandra/saved_caches/*<br /> then restarted cassandra on node1, wait 30 sec, then start cassandra on node 2, wait 1 min then run nodetool -h localhost ring:<br /> Address DC Rack Status State Load Owns Token<br /> 85070591730234615865843651857942052864<br /> 192.168.0.247 datacenter1 rack1 Up Normal 9.06 KB 50.00% 0<br /> 192.168.0.248 datacenter1 rack1 Up Normal 6.66 KB 50.00% 85070591730234615865843651857942052864</p> <p>Thank you!<br /> Best regards<br /> Thomas Augustinus </p> http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring#post-1872 Tue, 08 May 2012 18:47:45 +0000 nickmbailey 1872@http://www.datastax.com/support-forums/ <p>The cassandra data directories are configured in your cassandra.yaml. By default they are set to '/var/lib/cassandra'. I would reccommend deleting that directory on both nodes and starting with a completely clean install. </p> http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring#post-1871 Tue, 08 May 2012 18:44:45 +0000 Anonymous 1871@http://www.datastax.com/support-forums/ <p>That is very likely - I did not think of that!<br /> could you please guide me to the files / folders I need to delete?<br /> - or should I use a nodetool decomission?<br /> Thanks<br /> Thomas Augutinus </p> http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring#post-1870 Tue, 08 May 2012 18:32:50 +0000 nickmbailey 1870@http://www.datastax.com/support-forums/ <p>When you say 'cloned the first machine', do you mean completely cloned? When you start the first node it will save configuration files to the cassandra system tables. If those files exist when the second machine starts up, it could cause a problem like this. Make sure all data from your cassandra data directories is deleted when the second machine is started. </p> http://www.datastax.com/support-forums/topic/adding-second-node-removes-first-node-from-nodetool-ring#post-1869 Tue, 08 May 2012 18:13:43 +0000 Anonymous 1869@http://www.datastax.com/support-forums/ <p>Hi,</p> <p>I have installed cassandra on freebsd hyper-v virtual machine. The first node seems to be running ok with the following settings:<br /> cluster_name: 'Avargy Cluster'<br /> initial_token: 0<br /> seed_provider:<br /> - seeds: "192.168.0.247"<br /> listen_address: 192.168.0.247<br /> rpc_address: 192.168.0.247<br /> (the rest is at default settings)<br /> so - running "nodetool -h localhost ring" returns:<br /> Address DC Rack Status State Load Owns Token<br /> 192.168.0.247 datacenter1 rack1 Up Normal 22.21 KB 100.00% 0</p> <p>So, I cloned the first machine, changed ip, host-name in /etc/rc.conf and added a dns entry. The network connection works fine. I don't think that the clone is the related to the problem - just to complete the picture...<br /> I have disabled the firewall so it is not in the way :-)</p> <p>Now - I updated the cassandra.yaml script on the second node:<br /> initial_token: 85070591730234615865843651857942052864<br /> seed_provider:<br /> - seeds: "192.168.0.247"<br /> listen_address: 192.168.0.248<br /> rpc_address: 192.168.0.248<br /> (the rest is as node1)</p> <p>now - after starting cassandra I run "nodetool -h localhost ring" again (on node1):<br /> Address DC Rack Status State Load Owns Token<br /> 192.168.0.248 datacenter1 rack1 Up Normal 31.22 KB 100.00% 0</p> <p>So - apparently the new node "takes over"... and gets a token "0" - strange... :-(<br /> I expected (hoped) to see both nodes listed with each handling 50%... </p> <p>what do I do wrong?</p> <p>Thanks in advance!<br /> Thomas Augustinus </p>