You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/10/26 02:28:27 UTC
[jira] [Updated] (ACCUMULO-2145) Create upgrade test framework
[ https://issues.apache.org/jira/browse/ACCUMULO-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-2145:
---------------------------------
Status: Open (was: Patch Available)
Cancelling the patch on this as it's rather out of date. If there's renewed interest, let's pick it back up again!
> Create upgrade test framework
> -----------------------------
>
> Key: ACCUMULO-2145
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2145
> Project: Accumulo
> Issue Type: Test
> Reporter: Keith Turner
> Assignee: John McNamee
> Fix For: 1.7.1, 1.8.0
>
> Attachments: ACCUMULO-2145.v2.patch, ACCUMULO-2145.v3.patch, ACCUMULO-2145.v4.patch, 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.3.4#6332)