accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3590) Rolling upgrade support
Date Thu, 21 Jul 2016 20:05:21 GMT

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

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

bq. The SystemToken is created using properties of 'instance' to create a hash. Some of these
properties are created by default creating a unique hash between different versions.

Oh, we added new "instance.*" properties to the configuration between 1.6 and 1.7? Bummer.
We'll probably have to rethink how we compute the SystemToken in the future to account for
this scenario. Probably another sub-task for this umbrella.

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

Mime
View raw message