cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5102) upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other 1.2.0 nodes
Date Fri, 04 Jan 2013 17:46:13 GMT


Jonathan Ellis commented on CASSANDRA-5102:

The whole thing is a gotcha for assuming that we don't change messaging versions in minor
releases.  The futureproof version would have been {{if (!(version >= MessagingService.VERSION_12))}}
which looks kind of bizarre and might well have been "fixed" later on anyway.

So I'd file this under "if we have to take a mulligan and add another version mid-release-cycle,
make sure we validate usages of the initial major version."

And if we want to be extra careful we should probably include an unused version before new
major releases (i.e. make VERSION_20=8 instead of 7).
> upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other 1.2.0 nodes
> ----------------------------------------------------------------------------------------
>                 Key: CASSANDRA-5102
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Michael Kjellman
>            Assignee: Brandon Williams
>            Priority: Blocker
>             Fix For: 1.2.1
>         Attachments: 5102.txt
> I upgraded as I have since 0.86 and things didn't go very smoothly.
> I did a nodetool drain to my 1.1.7 node and changed my puppet config to use the new merged
config. When it came back up (without any errors in the log) a nodetool ring only showed itself.
I upgraded another node and sure enough now nodetool ring showed two nodes.
> I tried resetting the local schema. The upgraded node happily grabbed the schema again
but still only 1.2 nodes were visible in the ring to any upgraded nodes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message