You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/02/08 22:30:00 UTC

[jira] [Commented] (KUDU-2181) Multi-master config change support

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

ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------

Commit 3c363d499ec5c0d675d78d871712e579d966548c in kudu's branch refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=3c363d4 ]

[master] KUDU-2181 Raft ChangeConfig request to remove a master

This change adds RPC to request removal of an existing master from
a cluster. It builds on top of earlier change 9fc6c77 to add master.

Added tests for removal of non-leader master whether it's up
or down.

Change-Id: I76c03b8850faef60b65f85184c0a4db7cc6759ee
Reviewed-on: http://gerrit.cloudera.org:8080/16936
Reviewed-by: Alexey Serbin <as...@cloudera.com>
Tested-by: Bankim Bhavsar <ba...@cloudera.com>


> Multi-master config change support
> ----------------------------------
>
>                 Key: KUDU-2181
>                 URL: https://issues.apache.org/jira/browse/KUDU-2181
>             Project: Kudu
>          Issue Type: Improvement
>          Components: consensus, master
>            Reporter: Mike Percy
>            Assignee: Bankim Bhavsar
>            Priority: Major
>              Labels: roadmap-candidate
>
> It would be very useful to add support to the Kudu master for dynamic config change. The current procedure for replacing a failed master is fairly arduous.



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