Upgrade a node from 1.2.13 to 2.0.10 works correctly and we did run
upgradesstable on the new 2.0.x node.
The issue lies with the others nodes still running Cassandra 1.2.x
which failed to start if you did just a restart of the node.
Here is the describecluster output during the upgrade procedure
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
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
https://github.com/apache/cassandra/blob/cassandra-2.0/NEWS.txt#L195-L198
It's a good idea to move up to 2.0.12 while your at it. There have been a
nu
Hi,
we have a 52 Cassandra nodes cluster running Apache Cassandra 1.2.13.
As we are planning to migrate to Cassandra 2.0.10, we decide to do
some tests and we noticed that once a node in the cluster have been
upgraded to Cassandra 2.0.x, restarting a Cassandra 1.2.x will fail.
The tests were done
