[
https://issues.apache.org/jira/browse/KUDU-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wong reassigned KUDU-3294:
---------------------------------
Assignee: Andrew Wong
> ksck and rebalancer tools are useless if they can't resolve any of the
> tserver addresses
> ----------------------------------------------------------------------------------------
>
> Key: KUDU-3294
> URL: https://issues.apache.org/jira/browse/KUDU-3294
> Project: Kudu
> Issue Type: Bug
> Components: ops-tooling
> Reporter: Andrew Wong
> Assignee: Andrew Wong
> Priority: Major
>
> One of the first steps we perform when running {{ksck}} or the rebalancer
> tool is resolve the addresses of all tablet servers to initialize the proxies
> that will be used by each tool. If this step fails, the tool returns early,
> resulting in pitifully barren output along the lines of "an empty cluster",
> or simply a report that contains no tables, and not much to debug with other
> than a complaint like the following:
> {code:java}
> Network error: error fetching the cluster metadata from the leader master:
> unable to resolve address for <tserver>: Name or service not known {code}
> At worst, we should just skip over the tablet server and treat it as failed
> in the report.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
