[
https://issues.apache.org/jira/browse/HADOOP-17837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang resolved HADOOP-17837.
--------------------------------------
Fix Version/s: 3.4.0
Resolution: Fixed
Thanks [~bbeaudreault]. The PR is merged.
> Make it easier to debug UnknownHostExceptions from NetUtils.connect
> -------------------------------------------------------------------
>
> Key: HADOOP-17837
> URL: https://issues.apache.org/jira/browse/HADOOP-17837
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Most UnknownHostExceptions thrown throughout hadoop include a useful message,
> either the hostname that was not found or some other descriptor of the
> problem. The UnknownHostException thrown from NetUtils.connect only includes
> the [message of the underlyingÂ
> UnresolvedAddressException|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetUtils.java#L592].
> If you take a look at the source for UnresolvedAddressException, [it only
> has a no-args
> constructor|https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/nio/channels/UnresolvedAddressException.html]
> (java11, but same is true in other versions). So it never has a message,
> meaning the UnknownHostException message is empty.
> We should include the endpoint.toString() in the UnknownHostException thrown
> by NetUtils.connect
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
