[
https://issues.apache.org/jira/browse/HADOOP-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742383#comment-16742383
]
Steve Loughran commented on HADOOP-16044:
-----------------------------------------
bq With that said, if you have evidence this is a bad design, we should change
it.
no, I don't think it is a bad design. I'm curious. In a classic physical
deployment, DNS failures are a bad sign. And, because the JVM cached -ve DNS
results *forever* , spinning never fixed things. If the JVMs have stopped doing
this, then in a dynamic world, this makes sense.
I wondering something broader, which is: is the assumption that
"UnknownHostException not worth retrying" no longer valid?
And if so, what to do about all those existing uses?
> ABFS: Better exception handling of DNS errors followup
> ------------------------------------------------------
>
> Key: HADOOP-16044
> URL: https://issues.apache.org/jira/browse/HADOOP-16044
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Da Zhou
> Assignee: Da Zhou
> Priority: Major
> Attachments: HADOOP-16044-001.patch, HADOOP-16044-002.patch
>
>
> This is a follow up for HADOOP-15662 as the 001 patch of HADOOP-15662 is
> already committed.
--
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
