You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Da Zhou (JIRA)" <ji...@apache.org> on 2019/01/11 00:42:00 UTC
[jira] [Comment Edited] (HADOOP-15662) ABFS: Better exception
handling of DNS errors
[ https://issues.apache.org/jira/browse/HADOOP-15662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739903#comment-16739903 ]
Da Zhou edited comment on HADOOP-15662 at 1/11/19 12:41 AM:
------------------------------------------------------------
Submitting 002 patch:
- Log WARN level for failed request caused by hostNotFound exception and keep retrying.
- Manually verified the console out put for the failed request is in below format:
{code:java}
Can not reach host: fakef261500e-2296-4933-981d-544f0c9ab479.dfs.core.windows.net, retrying to solve the host name...
{code}
All tests passed my US west account:
XNS account oauth
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 22
Tests run: 168, Failures: 0, Errors: 0, Skipped: 21
XNS account sharedKey:
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 20
Tests run: 168, Failures: 0, Errors: 0, Skipped: 15
non-xns account sharedKe:
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 206
Tests run: 168, Failures: 0, Errors: 0, Skipped: 15
was (Author: danielzhou):
Submitting 002 patch:
- Log WARN level for failed request caused by hostNotFound exception.
- Manually verified the console out put for the failed request is in below format:
{code:java}
Can not reach host: fakef261500e-2296-4933-981d-544f0c9ab479.dfs.core.windows.net, retrying to solve the host name...
{code}
All tests passed my US west account:
XNS account oauth
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 22
Tests run: 168, Failures: 0, Errors: 0, Skipped: 21
XNS account sharedKey:
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 20
Tests run: 168, Failures: 0, Errors: 0, Skipped: 15
non-xns account sharedKe:
Tests run: 35, Failures: 0, Errors: 0, Skipped: 0
Tests run: 324, Failures: 0, Errors: 0, Skipped: 206
Tests run: 168, Failures: 0, Errors: 0, Skipped: 15
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org