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 2017/03/10 20:10:04 UTC

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

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

Adar Dembo resolved KUDU-422.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

bq. Mind if we close this one and just use the couple remaining subtasks to track the remaining work?

Works for me.


> 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
>             Fix For: 1.0.0
>
>
> 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.15#6346)