<?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: Cassandra 1.1.6 and 1.1.7.</title>
		<link>http://www.datastax.com/support-forums/topic/cassandra-116-and-117</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Sun, 19 May 2013 15:19:17 +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/cassandra-116-and-117" rel="self" type="application/rss+xml" />

		<item>
			<title>drohr on "Cassandra 1.1.6 and 1.1.7."</title>
			<link>http://www.datastax.com/support-forums/topic/cassandra-116-and-117#post-8052</link>
			<pubDate>Fri, 21 Dec 2012 10:08:18 +0000</pubDate>
			<dc:creator>drohr</dc:creator>
			<guid isPermaLink="false">8052@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;So, we where testing out to nuke one of our nodes in the cluster today (running 1.1.6) and upgrade that node to a bigger machine. When upgrade we noticed that we now got 1.1.7 installed, and that caused some issues.&#60;/p&#62;
&#60;p&#62;The entire cluster stopped working, and we got these kinds of errors on the new node:&#60;/p&#62;
&#60;p&#62;ERROR [MutationStage:22] 2012-12-21 09:41:30,132 RowMutationVerbHandler.java (line 61) Error in row mutation&#60;br /&#62;
org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find cfId=1011&#60;br /&#62;
        at org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySerializer.java:126)&#60;br /&#62;
        at org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(RowMutation.java:439)&#60;br /&#62;
        at org.apache.cassandra.db.RowMutation$RowMutationSerializer.deserialize(RowMutation.java:447)&#60;br /&#62;
        at org.apache.cassandra.db.RowMutation.fromBytes(RowMutation.java:395)&#60;br /&#62;
        at org.apache.cassandra.db.RowMutationVerbHandler.doVerb(RowMutationVerbHandler.java:42)&#60;br /&#62;
        at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59)&#60;br /&#62;
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)&#60;br /&#62;
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)&#60;br /&#62;
        at java.lang.Thread.run(Thread.java:662)&#60;/p&#62;
&#60;p&#62;When I killed the new node, downgraded to 1.1.6, then started it up again. No issues was found and everything was working again. Just a heads up.&#60;/p&#62;
&#60;p&#62;Using the RPM packages provided. apache-cassandra11-1.1.6 vs apache-cassandra11-1.1.7
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
