[
https://issues.apache.org/jira/browse/HDFS-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553467#comment-13553467
]
Tsz Wo (Nicholas), SZE commented on HDFS-4389:
----------------------------------------------
> The short-term workaround is to change the retry policy to be something else
> & to block for longer.
Yes, we may enable dfs.client.retry.policy.enabled. Then, the connection retry
policy will retry for ~11 minutes. (Or also change the default
dfs.client.retry.policy.spec if necessary.)
> Non-HA DFSClients do not attempt reconnects
> -------------------------------------------
>
> Key: HDFS-4389
> URL: https://issues.apache.org/jira/browse/HDFS-4389
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, hdfs-client
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Priority: Critical
>
> The HA retry policy implementation appears to have broken non-HA
> {{DFSClient}} connect retries. The ipc
> {{Client.Connection#handleConnectionFailure}} used to perform 45 connection
> attempts, but now it consults a retry policy. For non-HA proxies, the policy
> does not handle {{ConnectException}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
