To answer my own question: yes, the error is fatal. This also means that upgrades to 1.1.x from 1.0.x MUST use 1.0.11 or greater it seems to be successful.
My test upgrade from 1.0.9 to 1.1.5 left the cluster in a state that wasn't able to come to a schema agreement and blocked schema changes. -Bryan On Wed, Sep 12, 2012 at 2:42 PM, Bryan Talbot <btal...@aeriagames.com>wrote: > I'm testing upgrading a multi-node cluster from 1.0.9 to 1.1.5 and ran > into the error message described here: > https://issues.apache.org/jira/browse/CASSANDRA-4195 > > What I can't tell is if this is a serious issue or if it can be safely > ignored. > > If it is a serious issue, shouldn't the migration guides for 1.1.x require > that upgrades cannot be rolling or that all nodes must be running 1.0.11 or > greater first? > > > 2012-09-11 17:12:46,299 [GossipStage:1] ERROR > org.apache.cassandra.service.AbstractCassandraDaemon - Fatal exception in > thread Thread[GossipStage:1,5,main] > java.lang.UnsupportedOperationException: Not a time-based UUID > at java.util.UUID.timestamp(UUID.java:308) > at > org.apache.cassandra.service.MigrationManager.updateHighestKnown(MigrationManager.java:121) > at > org.apache.cassandra.service.MigrationManager.rectify(MigrationManager.java:99) > at > org.apache.cassandra.service.MigrationManager.onAlive(MigrationManager.java:83) > at org.apache.cassandra.gms.Gossiper.markAlive(Gossiper.java:806) > at > org.apache.cassandra.gms.Gossiper.handleMajorStateChange(Gossiper.java:849) > at > org.apache.cassandra.gms.Gossiper.applyStateLocally(Gossiper.java:908) > at > org.apache.cassandra.gms.GossipDigestAckVerbHandler.doVerb(GossipDigestAckVerbHandler.java:68) > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > > > -Bryan > >
