[
https://issues.apache.org/jira/browse/KUDU-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201707#comment-17201707
]
ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------
Commit 9fc6c772aff2bbfa008f52da8e7ba6e2c2d9012f in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=9fc6c77 ]
[master] KUDU-2181 Raft ChangeConfig request to add a master
This change:
- Adds hidden feature flag "--master_support_change_config" off by
default.
- RPC changes to add a master that initiates Raft config change and
responds asynchronously.
- RPC changes to report back member type(VOTER/NON_VOTER) of masters
- Removes the cached master_addresses in catalog manager as it's no
longer static.
- Updates and adds comments in MasterOptions such that it's used to
fetch master addresses only during master init time as masters can
be added/removed dynamically with this change.
- Updates ListMasters() to look at local Raft config instead of
MasterOptions as the masters can be added/removed dynamically.
If the new master can be caught up from the WAL then the master
gets promoted to VOTER else it remains as NON_VOTER without master
tablet copying support.
Change-Id: I0ac7e6e55220bcb01cad0fa386daaf656258088c
Reviewed-on: http://gerrit.cloudera.org:8080/16321
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Bankim Bhavsar <[email protected]>
> 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)
