cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9930) Add test coverage for 2.1 -> 3.0 upgrades
Date Fri, 14 Aug 2015 17:02:46 GMT

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

Russ Hatch commented on CASSANDRA-9930:
---------------------------------------

Test job here that overrides the upgrade path to test an upgrade direct from 2.1 to 3.0:

http://cassci.datastax.com/view/All_Jobs/job/cassandra_upgrade_2.1_direct_to_3.0/

We still need to separate noise from signal but this should be able to help us figure out
if it's working.

We can likely use a similar "manual override" approach for any special case upgrade paths
in the future.

> Add test coverage for 2.1 -> 3.0 upgrades
> -----------------------------------------
>
>                 Key: CASSANDRA-9930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9930
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ryan McGuire
>            Assignee: Russ Hatch
>             Fix For: 3.0.0 rc1
>
>
> Once we move to a [tick-tock model|http://www.mail-archive.com/dev%40cassandra.apache.org/msg07771.html]
we will need the ability to upgrade from stable release to stable release, skipping a single
version in the process.
> Example: 3.0 -> 3.2 (skipping the pass-through upgrade to 3.1 we normally have to
do)
> I would recommend we code this so that we can upgrade 2.1 directly to 3.0 as well, it's
probably too much work to do this for versions prior to that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message