Thanks for this confirmation Tyler. Would you guys consider this way of upgrading as a "best practice" to achieve a safe major release upgrade in the cloud (where you can easily add clusters and remove old ones) ?
I am seriously thinking about giving it a try for our upcoming 1.2 to 2.0 migration and see how things behave. See you around, Alain 2014-04-10 0:54 GMT+02:00 Tyler Hobbs <ty...@datastax.com>: > > On Tue, Apr 8, 2014 at 4:39 AM, Alain RODRIGUEZ <arodr...@gmail.com>wrote: > >> >> Yet, can't we rebuild a new DC with the current C* version, upgrade it to >> the new major once it is fully part of the C* cluster, and then switch all >> the clients to the new DC once we are sure everything is ok and shut down >> the old one ? >> > > Yes > > >> >> I mean, on a multiDC setup, while upgrading, there must be a moment that >> 2 DCs haven't the same major version, this is probably supported. >> > > It is supported, you just don't want to do add/remove nodes, run repairs, > etc with a mixed cluster. > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> >
