<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DataStax Support Forums &#187; Topic: nodetool ring different on each server after changing seeds</title>
		<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Sat, 18 May 2013 19:03:53 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.datastax.com/support-forums/search.php</link>
		</textInput>
		<atom:link href="http://www.datastax.com/support-forums/rss/topic/nodetool-ring-different-on-each-server-after-changing-seeds" rel="self" type="application/rss+xml" />

		<item>
			<title>Sven on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8962</link>
			<pubDate>Thu, 07 Feb 2013 00:56:08 +0000</pubDate>
			<dc:creator>Sven</dc:creator>
			<guid isPermaLink="false">8962@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hmm... that is sad. Do you want to try again, or are you out of patience?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>schalla on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8959</link>
			<pubDate>Thu, 07 Feb 2013 00:52:23 +0000</pubDate>
			<dc:creator>schalla</dc:creator>
			<guid isPermaLink="false">8959@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;No issues found after rollback. We are back on single NIC.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Sven on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8958</link>
			<pubDate>Wed, 06 Feb 2013 22:52:18 +0000</pubDate>
			<dc:creator>Sven</dc:creator>
			<guid isPermaLink="false">8958@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;And is the issue gone, or does it persist?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>schalla on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8952</link>
			<pubDate>Wed, 06 Feb 2013 22:33:53 +0000</pubDate>
			<dc:creator>schalla</dc:creator>
			<guid isPermaLink="false">8952@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I rolled back the complete change on all the three nodes.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>alexliu on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8943</link>
			<pubDate>Wed, 06 Feb 2013 17:01:52 +0000</pubDate>
			<dc:creator>alexliu</dc:creator>
			<guid isPermaLink="false">8943@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Can  you change the starting sequence of each nodes? Start hadoop node first. &#60;/p&#62;
&#60;p&#62;To isolate the issue, you can roll back the changes only for node 2 and restart all the nodes to check whether it's the configuration issue at node 2?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>schalla on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8940</link>
			<pubDate>Wed, 06 Feb 2013 14:10:50 +0000</pubDate>
			<dc:creator>schalla</dc:creator>
			<guid isPermaLink="false">8940@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Yes the NIC is perfectly connected and I can SSH over it. There is no typo in the seed or listen_address. I confirm.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Sven on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8934</link>
			<pubDate>Wed, 06 Feb 2013 04:57:02 +0000</pubDate>
			<dc:creator>Sven</dc:creator>
			<guid isPermaLink="false">8934@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Are you sure the NIC you are using can be used to see the other machines? One reason for this kind of issue could be that either that nic is not hooked up, or there is a firewall on. Did you check the ip address, could there be a type in the listen_address or seeds list?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>schalla on "nodetool ring different on each server after changing seeds"</title>
			<link>http://www.datastax.com/support-forums/topic/nodetool-ring-different-on-each-server-after-changing-seeds#post-8933</link>
			<pubDate>Wed, 06 Feb 2013 04:36:28 +0000</pubDate>
			<dc:creator>schalla</dc:creator>
			<guid isPermaLink="false">8933@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I have segregated gossip and thrift traffic on its own NIC's. I did change seeds and listen_address on a three node cluster. I did this while all the nodes were down. After starting with the new configuration, one of the node is not showing up in the ring as active. Below is the nodetool ring on each host. Nodes 1 and 3 are showing up correctly. Node 2 is dead from the cluster perspective. But the gossipinfo on Node 2 shows it is gossiping with other two nodes. Not sure where to start. Any ideas?&#60;br /&#62;
We are using DSE-2.2&#60;/p&#62;
&#60;p&#62;Node 1&#60;br /&#62;
Address         DC          Rack        Status State   Load            Owns                Token&#60;br /&#62;
                                                                                           113427455640312821154458202477256070485&#60;br /&#62;
192.168.2.101  Cassandra   rack1       Up     Normal  494.43 MB       33.33%              0&#60;br /&#62;
192.168.2.102  Analytics   rack1       Down   Normal  479.03 MB       33.33%              56713727820156410577229101238628035242&#60;br /&#62;
192.168.2.103  Solr        rack1       Up     Normal  491.57 MB       33.33%              113427455640312821154458202477256070485     &#60;/p&#62;
&#60;p&#62;Node 2&#60;br /&#62;
Address         DC          Rack        Status State   Load            Owns                Token&#60;br /&#62;
                                                                                           113427455640312821154458202477256070485&#60;br /&#62;
192.168.2.101  Analytics   rack1       Down   Normal  ?               33.33%              0&#60;br /&#62;
192.168.2.102  Analytics   rack1       Up     Normal  485.43 MB       33.33%              56713727820156410577229101238628035242&#60;br /&#62;
192.168.2.103  Analytics   rack1       Down   Normal  ?               33.33%              113427455640312821154458202477256070485 &#60;/p&#62;
&#60;p&#62;Node 3&#60;br /&#62;
Address         DC          Rack        Status State   Load            Owns                Token&#60;br /&#62;
                                                                                           113427455640312821154458202477256070485&#60;br /&#62;
192.168.2.101  Cassandra   rack1       Up     Normal  494.43 MB       33.33%              0&#60;br /&#62;
192.168.2.102  Analytics   rack1       Down   Normal  479.03 MB       33.33%              56713727820156410577229101238628035242&#60;br /&#62;
192.168.2.103  Solr        rack1       Up     Normal  491.57 MB       33.33%              113427455640312821154458202477256070485
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
