Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sun, 5 Apr 2015 05:38:33 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12774974.1423850754000.4660.1428212313146@Atlassian.JIRA>
In-Reply-To: <JIRA.12774974.1423850754000@Atlassian.JIRA>
References: <JIRA.12774974.1423850754000@Atlassian.JIRA>
 <JIRA.12774974.1423850754178@arcas>
Subject: [jira] [Updated] (ACCUMULO-3590) Rolling upgrade support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-3590:
---------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.8.0

> Rolling upgrade support
> -----------------------
>
>                 Key: ACCUMULO-3590
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3590
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Josh Elser
>             Fix For: 1.8.0
>
>
> We really lack any support for rolling upgrades between versions of Accumulo.
> Need to have a way to provide seamless upgrades between certain versions of Accumulo which minimize any downtime/impact on users of the system.
> Need to cover fundamental control features (like a rolling upgrade), changes to our serialized data structures (help prevent us from goofing up serialization across versions -- thrift/protobuf/etc), backwards/forward compatible RFile and WAL support (including control), lots of tests, and lots of documentation.


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