<?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: Different versions in a cassandra ring.</title>
		<link>http://www.datastax.com/support-forums/topic/different-versions-in-a-cassandra-ring</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Fri, 24 May 2013 16:45:29 +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/different-versions-in-a-cassandra-ring" rel="self" type="application/rss+xml" />

		<item>
			<title>tycen-medio on "Different versions in a cassandra ring."</title>
			<link>http://www.datastax.com/support-forums/topic/different-versions-in-a-cassandra-ring#post-7838</link>
			<pubDate>Wed, 05 Dec 2012 18:45:58 +0000</pubDate>
			<dc:creator>tycen-medio</dc:creator>
			<guid isPermaLink="false">7838@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I'm not an expert on this, but it worked fine for us short term to have different versions in the same ring.  I just upgraded 10 nodes from 0.7.9 to 1.1.6 and had the ring online while I did it - upgrading one node at a time.  You should also be able to do your plan of adding 6 new nodes with the new version then decommissioning the 6 old nodes.&#60;/p&#62;
&#60;p&#62;I think the bigger issue to look out for is any incompatibility issues between the versions your on and targeting.  This page had a good list of changes between versions - read the &#34;upgrading&#34; section of each version between your current version and your target version to make sure there isn't anything that will cause trouble: &#60;a href=&#34;https://github.com/apache/cassandra/blob/trunk/NEWS.txt&#34; rel=&#34;nofollow&#34;&#62;https://github.com/apache/cassandra/blob/trunk/NEWS.txt&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Good luck.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>sarch on "Different versions in a cassandra ring."</title>
			<link>http://www.datastax.com/support-forums/topic/different-versions-in-a-cassandra-ring#post-7731</link>
			<pubDate>Fri, 30 Nov 2012 09:49:48 +0000</pubDate>
			<dc:creator>sarch</dc:creator>
			<guid isPermaLink="false">7731@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I'm new to cassandra. How will a cluster handle nodes that are running different versions of cassandra?&#60;/p&#62;
&#60;p&#62;ie, will a cluster with nodes that are running both 1.0.11 and 1.0.12 work happily together. I would *assume* so but can't find information on the subject.&#60;/p&#62;
&#60;p&#62;Similarly, what about 1.1.5 and 1.1.6.&#60;/p&#62;
&#60;p&#62;And what about running 1.0.12 and 1.1.5 together.&#60;/p&#62;
&#60;p&#62;Obviously this is not an idea situation but would like to know what happens in this situation.&#60;/p&#62;
&#60;p&#62;I'm running a cluster in AWS and need to migrate to a newer version of cassandra. For repeatability we just launch a different AMI with the new version of cassandra installed on it.&#60;/p&#62;
&#60;p&#62;So if I have 6 nodes with cassandra 1.0.12 on it, is it a sensible migration strategy to launch 6 new nodes with cassandra 1.1.6 on them, join the ring (so it's got a total of 12 nodes), then decommission the original 6? Or is it best to manually upgrade the original cluster to 1.1.6, then do the same migration pattern (add new nodes to get cluster of 12, then decommission the old nodes).
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
