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 Wed, 09 Nov 2016 21:48:58 GMT

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

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

bq. Regarding this, what would the process for shutdown, upgrade, start up look like?

Exactly what you described. Some kind of shutdown step, upgrade of JARs on the given node,
and restart of that node again. Movement of tablets hosted by the node being upgrade is the
most difficult part to efficiently implement.

bq. My problem is that accumulo continually restarts the tablet server after a short interval
(give or take 2 minutes) when using stop-here.sh

Huh? Accumulo does not automatically restart services out of the box. There are ways that
you can configure the system to automatically restart stopped processes, but that's definitely
not standard functionality.

> 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: 2.0.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