Hi Roni, We had the same problem and had to build a new, separate cluster. We read from both clusters in the beginning and copied the data in the background by paging over our data in the old 2.1.3 cluster. This allowed us to make the downgrade seemless. Just watch out for 2.0.12's bug with nodetool cleanup and make sure you build the cluster with enough nodes so you don't need to add another node before version 2.0.13 gets released.
Best, Tobias On Fri, Mar 6, 2015 at 7:59 AM, Kai Wang <dep...@gmail.com> wrote: > AFAIK downgrading is not officially supported. > > how much data do you have? If all possible I would dump all my data out > and bulk load them into the 2.0.x cluster. This is the only way I feel safe. > On Mar 6, 2015 5:55 AM, "Roni Balthazar" <ronibaltha...@gmail.com> wrote: > >> Hi there, >> >> What is the best way to downgrade a C* 2.1.3 cluster to the stable 2.0.12? >> I know it's not supported, but we are getting too many issues with the >> 2.1.x... >> It is leading us to think that the best solution is to use the stable >> version. >> Is there a safe way to do that? >> >> Cheers, >> >> Roni >> >
