accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2145) Create upgrade test framework
Date Fri, 28 Feb 2014 16:30:20 GMT

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

Sean Busbey commented on ACCUMULO-2145:
---------------------------------------

bq. Can be configured to use existing HDFS and zookeeper instances

Just as a general concern, I'm going to want to use this against a live cluster, rather than
in psuedo distributed single node. That makes this particular part of the ticket description
important for my use case. Additionally, I'm going to want the Accumulo instance to be across
a cluster rather than a single node.

John, are you aiming to get either of those things included in this first pass? If not, I'd
like to make sure we get follow-on tickets made before closing this one out.

> Create upgrade test framework
> -----------------------------
>
>                 Key: ACCUMULO-2145
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2145
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: John McNamee
>         Attachments: updateTest.sh
>
>
> Accumulo upgrade testing in the past has been very minimal and mostly manual.  As a result
we have run into upgrade bugs in the past.   It would be nice to have a framework that makes
its easy to run and write upgrade test.  
>   * Can be configured to use existing HDFS and zookeeper instances
>   * Can be configured with 1.5.x and 1.6.x branches to build
>   * Supports multiple upgrade scenarios (like clean shutdown, dirty shutdown, etc)
>   * Runs a set of upgrade test (this would a be a list of test to run thats easy to add
to e.g. bulk import upgrade test)
> I am thinking the framework could do the following
>  {noformat}
>    1. Build or download a version of 1.5
>    2. Build or download a version of 1.6
>  
>    foreach scenario {
>       foreach upgrade test{
>            a. ask test for any 1.5 configuration
>            b. ask test for any 1.6 configuration
>            c. Unpack and configure 1.5  
>            d. Unpack and configure 1.6
>            e. Execute pre upgrade step of test
>            f. Execute scenario
>            g Execute post upgrade step of test
>       }
>    }
> {noformat} 
> The framework would configure the Accumulo versions, HDFS, zookeeper, and which test
to run.
> It would also be use to write the framework in such a way that it could support chaining
upgrade test.  For example run test that upgrades from 1.4 to 1.5 to 1.6.  It possible that
a fresh install of 1.5 will upgrade w/o problems, but a 1.5 system was upgraded to 1.4 will
not.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message