[
https://issues.apache.org/jira/browse/KUDU-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344893#comment-17344893
]
ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------
Commit 207e4e693beb37c1f44c7621b244198bdbe895c1 in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=207e4e6 ]
[master] KUDU-2181 Unhide master change config flag & other improvements
This change:
- Unhides and turns the master Raft change config flag ON by default
- Updates the description of flags that are not passed to the new
master
- Uses sync logging on bringing up the new master to help
debug any issues in startup of the new master
- Updates the wait timeout while bringing up a new master to account
for the higher ntp wait timeout. This timeout is also used for
checking whether the new master's system catalog has caught up
from WAL. So this'll bump up timeout for that case as well. Thought
about introducing separate wait timeout for that case but felt like
exposing too many knobs and user shouldn't care whether time
is being taken for master bringup or catchup from WAL.
Change-Id: Id1fc1dc5985601158ae58d5d190a60c1e542ea1d
Reviewed-on: http://gerrit.cloudera.org:8080/17401
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-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)
