[ https://issues.apache.org/jira/browse/HDFS-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552611#comment-13552611 ]
Steve Loughran commented on HDFS-4389: -------------------------------------- I think old retry policy used to be longer than 30s, so a restart of a small-mid cluster may not have been noticed The short-term workaround is to change the retry policy to be something else & to block for longer. > 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