[
https://issues.apache.org/jira/browse/KUDU-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260502#comment-17260502
]
ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------
Commit 47075a180ca46366a56af2ff97f65b199b4a1f4e in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=47075a1 ]
[master] KUDU-2181 Procedure for copying sys catalog on adding master
This change outlines procedure to copy system catalog for the newly
added master using existing CLI tools and the master ChangeConfig RPC.
Only functional change is to hookup the master runtime flag
--master_consensus_allow_status_msg_for_failed_peer to Raft consensus.
New master could go into a FAILED_RECOVERABLE state if the leader
master's system catalog WAL has been GC'ed. This change allows the
new master to be promoted after copying the system catalog externally.
Outline of the test procedure:
1) Runtime flag --master_consensus_allow_status_msg_for_failed_peer
must be turned on for existing masters.
2) Start the new master with
--master_address_add_new_master=<new-master-hostport> and
--master_addresses that contains itself and existing masters.
3) Invoke ChangeConfig to add the master.
4) Verify the new master is part of the Raft config even if it's a
LEARNER/NON_VOTER or goes into FAILED_RECOVERABLE state. If not,
above steps will have to be repeated.
5) If the new master is promoted to being a VOTER then following tablet
copy steps can be skipped.
6) Shutdown the new master.
7) Delete the system catalog on the new master.
8) Copy the system catalog from the leader master to the new master.
9) Bring up the new master.
10) Verify the new master is promoted as VOTER.
If the new master doesn't get promoted to a VOTER then double check
whether the new master is part of the Raft config for masters by
running "kudu master list".
- If yes, repeat procedure from step 6.
- Else repeat the entire procedure
Change-Id: I142c1dec442ec72c38c5be9d62cdf270e441d6e3
Reviewed-on: http://gerrit.cloudera.org:8080/16830
Tested-by: Kudu Jenkins
Reviewed-by: Bankim Bhavsar <ban...@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)
