Hello All, I've asked this on the Cassandra IRC channel earlier, but I am asking the list as well so that I get feedback from more people.
We have recently upgraded from Cassandra 1.2.19 to 2.0.16 and we are currently in the stage where all boxes are running 2.0.16 but nt upgradesstables has not yet been performed on all of them. Reading the DataStax docs [1] : - Do not issue these types of queries during a rolling restart: DDL, TRUNCATE In our case the restart bit has already been done. Do you know if it would be a bad idea to create a new KS before all nodes have upgraded their SSTables? Our concern is the time it takes to go through every single node, run the upgradesstables and wait until it's all done. We think creating a new KS wouldn't be a problem (someone on the channel said the same thing, but recommended that we play safe and wait until it's all done). But if anyone has any catastrophic experiences in doing so we would appreciate their input. Many thanks, Vasilis [1] http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html
