[
https://issues.apache.org/jira/browse/KUDU-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352051#comment-17352051
]
ASF subversion and git services commented on KUDU-2181:
-------------------------------------------------------
Commit 04262dc8d20ac441890971d8487eda586fdbe43e in kudu's branch
refs/heads/branch-1.15.x from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=04262dc ]
[master] KUDU-2181 Fix duplicate master address and remove unsafe flag tag
While testing add master on a physical cluster, observed that
supplying only hostnames without port resulted in duplicates
being supplied to bring up new master which in turn leads
to failure in creating distributed Raft config on startup.
For e.g. kudu master add hp1,hp2 h2
Reason being hp2 is compared as hp2:7051 whereas in the vector
of strings "master_addresses", it contains hp1,hp2.
This changes adds a new function ParseAddresses() in HostPort class
that's a variant of existing ParseStrings() function and takes
a vector of strings instead. This new function is used
in the duplicate detection logic.
This change also removes the unsafe tag from
--master_addr_add_new_master as the feature is ready but keeps
it hidden as it's only meant to be used by the add master orchestration
tool.
This one is tricky to test locally and write a test because
we need to specify ports for starting masters/tservers.
Verified the fix on physical cluster. Along with CM integration
we can add a systest later.
Change-Id: Icf29730e3a6b225adb24ff161cac2ad777b46b81
Reviewed-on: http://gerrit.cloudera.org:8080/17500
Tested-by: Bankim Bhavsar <ban...@cloudera.com>
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
(cherry picked from commit 261d71ef71fcfdf96c26c9d604d6fc0147c2ee6a)
Reviewed-on: http://gerrit.cloudera.org:8080/17516
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)
