cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13384) Legacy caching options can prevent 3.0 upgrade
Date Tue, 28 Mar 2017 22:14:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946064#comment-15946064
] 

Jeremiah Jordan commented on CASSANDRA-13384:
---------------------------------------------

So I did some more investigation here with some test upgrades myself and after creating a
table on 2.0 and upgrading to 2.1 the schema seemingly has the correct json formatted thing
in it.  But if you then immediately upgrade to 3.0 with a kill -9 stop, 3.0 fails to start.
 If you instead flush before upgrading to 3.0 the json version of the schema is flushed to
disk, and everything is fine.  I'm not sure it is worth adding ugly legacy conversion hacks
in 3.x for this super edge case of "upgrade as fast as I can without flushing".

> Legacy caching options can prevent 3.0 upgrade
> ----------------------------------------------
>
>                 Key: CASSANDRA-13384
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13384
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Schema
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>            Priority: Minor
>             Fix For: 3.0.x, 3.11.x
>
>
> In 2.1, we wrote caching options as a JSONified map, but we tolerated raw strings ["ALL",
"KEYS_ONLY", "ROWS_ONLY", and "NONE"|https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/cache/CachingOptions.java#L42].
> If a 2.1 node with any of these strings is upgraded to 3.0, the legacy schema migration
will fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message