On Tue, Jan 8, 2013 at 8:41 AM, Todd Nine <todd.n...@gmail.com> wrote: > I have recently been trying to restore backups from a v1.0.x cluster we > have into a 1.1.7 cluster. This has not been as trivial as I expected, and > I've had a lot of help from the IRC channel in tackling this problem. As a > way of saying thanks, I'd like to contribute the updated ruby script I was > originally given for accomplishing this task. Here it is.
While I laud your contribution, I am still not fully understanding why this is not working "automagically", as it should : http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-1-flexible-data-file-placement " What about upgrading? Do you need to manually move all pre-1.1 data files to the new directory structure before upgrading to 1.1? No. Immediately after Cassandra 1.1 starts, it checks to see whether it has old directory structure and migrates all data files (including backups and snapshots) to the new directory structure if needed. So, just upgrade as you always do (don’t forget to read NEWS.txt first), and you will get more control over data files for free. " Is it possible that, for example, the installation of the debian package results in your 1.1.x node starting up before you intend it to.. and then when you start it again with the 1.0 paths, it doesn't try to change the paths? " * To check if sstables needs migration, we look at the System directory. If it contains a directory for the status cf, we'll attempt a sstable migrating. " This quote from Directories.java (thx driftx!) suggests that any starting of a 1.1 node, which would result in a "Status" columnfamily being created, would make sstablesNeedsMigration return false. If this is your case due to the use of the debian package or similar which auto-starts, your input is welcomed at : https://issues.apache.org/jira/browse/CASSANDRA-2356 =Rob -- =Robert Coli AIM>ALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
