Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Casey Deccio
On Tue, May 15, 2012 at 5:41 PM, Dave Brosius wrote: > The replication factor for a keyspace is stored in the > system.schema_keyspaces column family. > > Since you can't view this with cli as the server won't start, the only way > to look at it, that i know of is to use the > > sstable2json tool

Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Dave Brosius
The replication factor for a keyspace is stored in the system.schema_keyspaces column family. Since you can't view this with cli as the server won't start, the only way to look at it, that i know of is to use the sstable2json tool on the *.db file for that column family... So for instance on

Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Casey Deccio
Sorry to reply to my own message (again). I took a closer look at the logs and realized that the partitioner errors aren't what kept the daemon to stop; those errors are in the logs even before I upgraded. This one seems to be the culprit. java.lang.reflect.InvocationTargetException at s

Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Casey Deccio
cassandra.yaml on all nodes had ByteOrderedPartitioner with both the previous version and upgraded version. That being said, when I first started up cassandra after upgrading (with the updated .yaml, including ByteOrderedPartitioner) all nodes in the ring appeared to be up. But the load they car

Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Oleg Dulin
Did you check cassandra.yaml to make sure partitioner there matches what was in your old cluster ? Regards, Oleg Dulin Please note my new office #: 732-917-0159 On May 15, 2012, at 3:22 PM, Casey Deccio wrote: > Here's something new in the logs: > > ERROR 12:21:09,418 Exception in thread Threa

Re: cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Casey Deccio
Here's something new in the logs: ERROR 12:21:09,418 Exception in thread Thread[SSTableBatchOpen:2,5,main] java.lang.RuntimeException: Cannot open /var/lib/cassandra/data/system/Versions/system-Versions-hc-35 because partitioner does not match org.apache.cassandra.dht.ByteOrderedPartitioner

cassandra upgrade to 1.1 - migration problem

2012-05-15 Thread Casey Deccio
I recently upgraded from cassandra 1.0.10 to 1.1. Everything worked fine in one environment, but after I upgraded in another, I can't find my keyspace. When I run, e.g., cassandra-cli with 'use KeySpace;' It tells me that the keyspace doesn't exist. In the log I see this: ERROR [MigrationStage: