That sounds about right for changing the CF type, you'll need to drop the existing CF first. You should be able to drop the existing CF from the nodes as a rolling change and and add the new super CF as a rolling change as well. Or if you can shutdown, shutdown and delete the existing CF, restart a
Thank you for your comments.
You are right we are running 0.6.4, and we are changing column family type
to supercolumn.
So the idea is to export data, stop all the nodes in the ring, remove data
files, restart all nodes with the new storage-conf and reimport data.
Jean-Yves
On Wed, Oct 13, 2010
I've always assumed that when the drain command logs that the node is drained
the commit log is clear. The drain command stops the node from accepting
requests, flushes the memtables to disk and finally marks the commit logs as
safe to delete. As far as I can tell, it should either work or fail.
Hi all,
When I look at the wiki the procedure to change the column family is :
1. Empty the commitlog with "nodetool drain."
2. Shutdown Cassandra and verify that there is no remaining data in the
commitlog.
3. Delete the sstable files (-Data.db, -Index.db, and -Filter.db) for any
