You probably want to go to 1.0.11/12 first no matter what. If you want the least chance of issue you should then go to 1.1.12. While there is a high probability that going from 1.0.X->1.2 will work. You have the best chance at no failures if you go through 1.1.12. There are some edge cases that can cause errors if you don't do that.
-Jeremiah On Aug 30, 2013, at 11:41 AM, Mike Neir <m...@liquidweb.com> wrote: > In my testing, mixing 1.0.9 and 1.2.8 seems to work fine as long as there is > no need to do streaming operations (move/repair/bootstrap/etc). The reading > I've done confirms that 1.2.x should be network-compatible with 1.0.x, sans > streaming operations. Datastax seems to indicate here that doing a rolling > upgrade from 1.0.x to 1.2.x is viable: > > http://www.datastax.com/documentation/cassandra/1.2/webhelp/#upgrade/upgradeC_c.html#concept_ds_nht_czr_ck > > See the second bullet point in the Prerequisites section. > > I'll look into 1.2.9. It wasn't available when I started my testing. > > MN > > On 08/30/2013 12:15 PM, Robert Coli wrote: >> On Fri, Aug 30, 2013 at 8:57 AM, Mike Neir <m...@liquidweb.com >> <mailto:m...@liquidweb.com>> wrote: >> >> I'm faced with the need to update a 36 node cluster with roughly 25T of >> data >> on disk to a version of cassandra in the 1.2.x series. While it seems that >> 1.2.8 will play nicely in the 1.0.9 cluster long enough to do a rolling >> upgrade, I'd still like to have a roll-back plan in case the rolling >> upgrade >> goes sideways. >> >> >> Upgrading two major versions online is an unsupported operation. I would not >> expect it to work. Is there a detailed reason you believe it should work >> between >> these versions? Also, instead of 1.2.8 you should upgrade to 1.2.9, released >> yesterday. Everyone headed to 2.0 has to pass through 1.2.9. >> >> =Rob > > -- > > > > Mike Neir > Liquid Web, Inc. > Infrastructure Administrator >
