You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2016/08/16 01:37:20 UTC

[jira] [Resolved] (KUDU-1474) Provide a mechanism to migrate from single to multiple masters

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

Adar Dembo resolved KUDU-1474.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.0)
                   0.10.0

Fixed in commit 98fe55f.

> Provide a mechanism to migrate from single to multiple masters
> --------------------------------------------------------------
>
>                 Key: KUDU-1474
>                 URL: https://issues.apache.org/jira/browse/KUDU-1474
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: master
>    Affects Versions: 0.8.0
>            Reporter: Adar Dembo
>            Assignee: Adar Dembo
>            Priority: Critical
>             Fix For: 0.10.0
>
>
> We need a mechanism to convert a single-master setup into a multi-master setup. It'll probably rely on remote bootstrap in some capacity, and could conceivably be used to repair a master in the event that it needs to be rebuilt.
> I haven't given this any thought. I'm also wondering out loud whether such a mechanism would be sufficient for a CLI tool that adds new masters or removes old masters from a Raft configuration.



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