Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 9 Jul 2016 18:15:11 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12774974.1423850754000.67441.1468088111150@Atlassian.JIRA>
In-Reply-To: <JIRA.12774974.1423850754000@Atlassian.JIRA>
References: <JIRA.12774974.1423850754000@Atlassian.JIRA> <JIRA.12774974.1423850754178@arcas>
Subject: [jira] [Commented] (ACCUMULO-3590) Rolling upgrade support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 09 Jul 2016 18:15:13 -0000


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

Josh Elser commented on ACCUMULO-3590:
--------------------------------------

I don't believe we have made any changes between any 1.6 and 1.7 release which would prevent this from working. However, it hasn't been tested, so YMMV.

> 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.9.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)