Thanks for the pointer Fabien.
From: Fabien Rousseau <fab...@yakaz.com<mailto:fab...@yakaz.com>> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Date: Friday, June 28, 2013 6:35 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: Errors while upgrading from 1.1.10 version to 1.2.4 version Hello, Have a look at : https://issues.apache.org/jira/browse/CASSANDRA-5476 2013/6/28 Ananth Gundabattula <agundabatt...@threatmetrix.com<mailto:agundabatt...@threatmetrix.com>> Hello Everybody, We were performing an upgrade of our cluster from 1.1.10 version to 1.2.4 . We tested the upgrade process in a QA environment and found no issues. However in the production node, we faced loads of errors and had to abort the upgrade process. I was wondering how we ran into such a situation. The main difference between the QA environment and the production environments is the Replication Factor. In QA , RF=1 and in production RF=3. Example stack traces are as seen on the other nodes are : http://pastebin.com/fSnMAd8q The other observation is that the node which was being upgraded is a seed node in the 1.1.10. We aborted right after the first node gave the above issues. Does this mean that there will be an application downtime required if we go for rolling upgrade on a live cluster from 1.1.10 version to 1.2.4 version ? Regards, Ananth -- Fabien Rousseau [http://www.yakaz.com/img/logo_yakaz_small.png] <mailto:aur...@yakaz.com>www.yakaz.com<http://www.yakaz.com/>
