[
https://issues.apache.org/jira/browse/HADOOP-15662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740600#comment-16740600
]
Da Zhou commented on HADOOP-15662:
----------------------------------
[~tmarquardt]
L73: Will fix the msg format.
BTW, the HostNotFountException.getMessage() will only print out the unresolved
host name, just as "httpOperation.getUrl().getHost())" does.
L714: I see what you mean, yes the else if will break the exception trace.
[~ste...@apache.org]
Sorry, I will open a new jira for this follow up, closing this one.
> ABFS: Better exception handling of DNS errors
> ---------------------------------------------
>
> Key: HADOOP-15662
> URL: https://issues.apache.org/jira/browse/HADOOP-15662
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Reporter: Thomas Marquardt
> Assignee: Da Zhou
> Priority: Major
> Fix For: 3.2.1
>
> Attachments: HADOOP-15662-001.patch, HADOOP-15662-002.patch
>
>
> DNS errors are common during testing due to typos or misconfiguration. They
> can also occur in production, as some transient DNS issues occur from time to
> time.
> 1) Let's investigate if we can distinguish between the two and fail fast for
> the test issues, but continue to have retry logic for the transient DNS
> issues in production.
> 2) Let's improve the error handling of DNS failures, so the user has an
> actionable error message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
