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/13 20:26:22 UTC

[jira] [Resolved] (KUDU-850) Add a test which proves it's possible to migrate from single-master to multi-master

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

Adar Dembo resolved KUDU-850.
-----------------------------
       Resolution: Fixed
         Assignee: Mike Percy  (was: Adar Dembo)
    Fix Version/s: 0.10.0

Mike ended up changing the default master to be single-node Raft. We're already using KUDU-1474 to track the addition of a migration mechanism, so I'll close this.


> Add a test which proves it's possible to migrate from single-master to multi-master
> -----------------------------------------------------------------------------------
>
>                 Key: KUDU-850
>                 URL: https://issues.apache.org/jira/browse/KUDU-850
>             Project: Kudu
>          Issue Type: Improvement
>          Components: consensus, test
>    Affects Versions: GA
>            Reporter: Todd Lipcon
>            Assignee: Mike Percy
>             Fix For: 0.10.0
>
>
> In theory, one could take a LocalConsensus WAL and use that in RaftConsensus to start a multi-node setup. We don't have any tests that prove this, though, and may need some more tooling (eg to add consensus metadata on disk).
> We should either do this, or change the default master to be a single-node Raft.



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