You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Andrew Wong (Jira)" <ji...@apache.org> on 2020/06/02 18:47:00 UTC

[jira] [Resolved] (KUDU-2054) Rolling Restart and Upgrade

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

Andrew Wong resolved KUDU-2054.
-------------------------------
    Fix Version/s: 1.12.0
       Resolution: Fixed

Rolling restart is documented here [https://github.com/apache/kudu/commit/161dec9]

> Rolling Restart and Upgrade
> ---------------------------
>
>                 Key: KUDU-2054
>                 URL: https://issues.apache.org/jira/browse/KUDU-2054
>             Project: Kudu
>          Issue Type: Wish
>            Reporter: Alan Jackoway
>            Assignee: Andrew Wong
>            Priority: Major
>              Labels: roadmap-candidate
>             Fix For: 1.12.0
>
>
> It would be helpful for our operations if Kudu supported rolling restart and rolling upgrade by some process of restarting tablet servers + masters one by one or in batches less than the replication size.
> This would allow us to continue using Kudu during an upgrade or restart the way we can with HBase or HDFS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)