[HADOOP-17837] Make it easier to debug UnknownHostExceptions from NetUtils.connect

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.2
• Fix Version/s: 3.4.0, 3.3.2
• Component/s: common
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.3.2
• Hadoop Flags: Reviewed
• Assignee: Bryan Beaudreault
• Reporter: Bryan Beaudreault
• Created: 05/Aug/21 19:30
• Updated: 11/Feb/24 09:18
• Resolved: 06/Aug/21 16:30

Description

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. If you take a look at the source for UnresolvedAddressException, it only has a no-args constructor (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

Issue Links

• links to: GitHub Pull Request #3272
• links to: GitHub Pull Request #3276

Sub-Tasks

• Backport HADOOP-17837 to branch-3.2: Resolved