Re: Downgrade Cassandra from 2.1.x to 2.0.x

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 nodeto

Re: Issue restarting cassandra with a cluster running Cassandra 1.2.x and Cassandra 2.0.x

I would recommend against 2.0.12 as long as nodetool cleanup is broken and wait for 2.0.13. On Tue, Mar 3, 2015 at 11:43 AM, Nate McCall wrote: > Did you run 'upgrade sstables'? See these two sections in 2.0's NEWS.txt: > https://github.com/apache/cassandra/blob/cassandra-2.0/NEWS.txt#L132-L141

Nodetool cleanup on 2.0.12 doesn't work

Hi, We have a small cluster running 2.0.12 and after adding a new node to it running nodetool cleanup fails on every old node with "AssertionError: Memory was freed". It seems to be fixed in 2.0.13, see https://issues.apache.org/jira/browse/CASSANDRA-8716. Is there any workaround for this in 2.0.1

Re: Moving from 2.1.x to 2.0.x

Thanks, Tobias On Fri, Feb 20, 2015 at 11:28 AM, Robert Coli wrote: > On Fri, Feb 20, 2015 at 9:25 AM, Tobias Hauth > wrote: > >> Is there an recommended way of moving data from a 2.1.x cluster to a >> 2.0.x cluster? We would like to downgrade to a more stable version of

Moving from 2.1.x to 2.0.x

Hi, Is there an recommended way of moving data from a 2.1.x cluster to a 2.0.x cluster? We would like to downgrade to a more stable version of C* and just adding nodes with C* 2.0.12 results in schema miss-matches and 'nodetool describecluster' reports different schema versions. Thanks, Tobias