[
https://issues.apache.org/jira/browse/KUDU-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-2884.
-------------------------------
Fix Version/s: 1.14.0
Assignee: Grant Henke
Resolution: Fixed
> 'kudu hms fix' CLI tool mistakenly reports on non-matching master addresses
> ---------------------------------------------------------------------------
>
> Key: KUDU-2884
> URL: https://issues.apache.org/jira/browse/KUDU-2884
> Project: Kudu
> Issue Type: Bug
> Components: CLI, hms
> Reporter: Alexey Serbin
> Assignee: Grant Henke
> Priority: Major
> Fix For: 1.14.0
>
>
> When running the {{kudu hms fix}} against a Kudu cluster with managed Kudu
> tables created via {{impala-shell}}, the tool misinterprets master addresses
> being non-equal since from one side it gets the addresses with the default
> port number from CLI context, and from the other side the default port number
> is omitted (HMS metainfo). As a result, the tool output an error and fails.
> {noformat}
> sudo -u kudu kudu hms fix a.b.c.com --drop_orphan_hms_tables
> --ignore_other_clusters=false
> I0630 17:29:55.427356 3689 tool_action_hms.cc:602] Skipping drop of orphan
> HMS table db_name.table_name with master addresses parameter a.b.c.com
> because it does not match the --master_addresses argument (use --force to
> skip this check)
> {noformat}
> Running the tool with {{--force}} might might introduce some issues if there
> are some table which indeed have different set of master addresses recorded
> in their HMS metadata.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
