[
https://issues.apache.org/jira/browse/KUDU-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Chovan reassigned KUDU-3550:
-----------------------------------
Assignee: Zoltan Chovan
> Improve master RPC address comparison in the 'kudu hms check' CLI tool
> ----------------------------------------------------------------------
>
> Key: KUDU-3550
> URL: https://issues.apache.org/jira/browse/KUDU-3550
> Project: Kudu
> Issue Type: Improvement
> Components: CLI
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Assignee: Zoltan Chovan
> Priority: Major
>
> The {{kudu hms check}} CLI tool treats RPC addresses with and without default
> master RPC port 7051 as different ones, even if those are the same in fact.
> That leads to bogus warnings when running the tool with the list of masters
> the same as in the Kudu table's HMS entry, differing only in presence/absence
> of the default master RPC port 7051.
> For example, if the table 'db.my_table' had master1,master2,master3 as the
> list of Kudu masters, running {{kudu hms check
> master1:7051,master2:7051,master3:7051}} would output the following:
> {noformat}
> I0205 14:22:28.166532 1053705 tool_action_hms.cc:432] Skipping HMS table
> db.my_table with different masters specified: master1,master2,master3
> {noformat}
> It would be nice to make the tool comparing master addresses in a more
> intelligent way, so that Kudu master RPC addresses that differ only in
> presence of the master default RPC port treated as same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
