[
https://issues.apache.org/jira/browse/KUDU-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17326047#comment-17326047
]
ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------
Commit d5d8fadadac750bd9a71c4bc928dc7de05168a9a in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=d5d8fad ]
[master][tool] KUDU-2181 Tool to orchestrate adding a master
This tool orchestrates the mechanism to add a master to an existing
Kudu cluster using the changes made previously including the add master
Raft change config.
This tool must be run from the master being added.
Outline of steps:
- Bring up master from supplied flags
- Invoke add master Raft change config RPC
- Determine whether new master has caught up from WAL
and ksck is healthy.
- If yes, we are done else continue below
- Delete system catalog on the new master
- Copy system catalog from one of the existing masters
- Verify ksck is healthy.
- Shutdown the new master
The tool now manages bringing up the new master process, copying
system catalog and hence bunch of functionality from the
dynamic_multi_master test is no longer needed and hence deleted.
Using Subprocess we need to shutdown the new master and hence can't
verify certain state which included contacting new master directly
immediately after adding new master. Function
VerifyClusterAfterMasterAddition() covers comprehensive verification
steps so not missing out by removing those steps.
This change also includes some refactoring in ExternalDaemon
to fetch Kerberos related configuration to be used outside
ExternalMiniCluster.
Change-Id: I8f99cf2b3f1738c4127c7e7288beab61daf42e7b
Reviewed-on: http://gerrit.cloudera.org:8080/17267
Reviewed-by: Andrew Wong <aw...@cloudera.com>
Tested-by: Kudu Jenkins
> 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)
