[jira] [Commented] (KUDU-422) Replicated master process (no master SPOF)

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on KUDU-422:
----------------------------------

[~adar] - I started trying to play with multi-master on a cluster today. one thing I'm not sure if it's tracked yet: how can someone convert from a single master to a multi-master setup? Seems like we might need some startup mode to do the conversion (eg starting the other masters with a '--bootstrap-from' flag or something like that?) This same process might be usable to "repair" a master that had to be rebuilt.

> Replicated master process (no master SPOF)
> ------------------------------------------
>
>                 Key: KUDU-422
>                 URL: https://issues.apache.org/jira/browse/KUDU-422
>             Project: Kudu
>          Issue Type: New Feature
>          Components: consensus, master
>    Affects Versions: M5
>            Reporter: Todd Lipcon
>            Assignee: Adar Dembo
>            Priority: Critical
>              Labels: kudu-roadmap
>
> Support for multiple masters with consensus-replicated data. Goal is to have to be able to do manual failovers if the leader of the master quorum dies, stretch goal for this milestone is to have that failover happen unattended.



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