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

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

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

[tool] KUDU-2181 CLI to remove master

This change adds CLI to remove master from the cluster
which in turn invokes the RemoveMaster ChangeConfig RPC.

This CLI will be part of the workflow to remove master
from an existing cluster or recover dead master at the
same HostPort.

Change-Id: I5c97b03475b0ffc7b387d7dfc17acc4b13858fb7
Reviewed-on: http://gerrit.cloudera.org:8080/17010
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Bankim Bhavsar <ban...@cloudera.com>
Reviewed-by: Andrew Wong <aw...@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)

Reply via email to