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] [Created] (CASSANDRA-7746) fix upgrade_through_versions local mode for rolling upgrades
Date Mon, 11 Aug 2014 17:22:12 GMT
Russ Hatch created CASSANDRA-7746:
-------------------------------------

             Summary: fix upgrade_through_versions local mode for rolling upgrades
                 Key: CASSANDRA-7746
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7746
             Project: Cassandra
          Issue Type: Test
            Reporter: Russ Hatch
            Priority: Minor


Upgrade tests now have a local mode for easier debugging with local code modifications (instead
of fetching remote versions). This works by locally changing branches and building cassandra
as needed.

There's a potential problem for rolling upgrades because the code will be updated while some
of the nodes are still using the last version. I'm not certain if this really affects much
in practice but should be relatively straightforward to fix.

Instead of switching branches, the tests will need to check out the target branch/tag to another
location on the filesystem. When upgrading, another version will be checked out to another
location on the filesystem, etc. To keep this (hopefully) platform agnostic we should be able
to use the python tempfile module, and git can probably be used to check out a single branch
as described here: http://stackoverflow.com/questions/1778088/how-to-clone-a-single-branch-in-git



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message