We went from 1.1.4 to 1.2.2 and in QA rolling restart failed but in production and QA bringing down the whole cluster upgrading every node and then bringing it back up worked fine. We left ours at randompartitioner and had LCS as well. We did not convert to Vnodes at all. Don't know if it helps at all, but it is a similar case I would think.
Dean From: Wei Zhu <wz1...@yahoo.com<mailto:wz1...@yahoo.com>> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>, Wei Zhu <wz1...@yahoo.com<mailto:wz1...@yahoo.com>> Date: Tuesday, April 23, 2013 12:11 PM To: Cassandr usergroup <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: move data from Cassandra 1.1.6 to 1.2.4 Hi, We are trying to upgrade from 1.1.6 to 1.2.4, it's not really a live upgrade. We are going to retire the old hardware and bring in a set of new hardware for 1.2.4. For old cluster, we have 5 nodes with RF = 3, total of 1TB data. For new cluster, we will have 10 nodes with RF = 3. We will use VNodes. What is the best way to bring the data from 1.1.6 to 1.2.4? A couple of concerns: * We also use LCS and plan to increase SSTable size. * We use randomPartitioner, we should stick with it, not to mess up with murmur3? Thanks for your feedback. -Wei
