<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: hdfs client takes 20s to failover to alternate namenode in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/hdfs-client-takes-20s-to-failover-to-alternate-namenode/m-p/269564#M206928</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you find a solution ? I have the same problem with my production cluster.&lt;/P&gt;&lt;P&gt;HDFS HA is implemented from several years without problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But recently,&amp;nbsp;we realized that a hdfs client have to wait 20 secondes when the server hosting the nn1 is shutdown. Exemple when I set the debug mode :&lt;/P&gt;&lt;P&gt;&lt;EM&gt;19/08/29 11:03:05 DEBUG ipc.Client: Connecting to XXXXX/XXXXX:8020&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;19/08/29 11:03:23 DEBUG ipc.Client: Failed to connect to server: XXXXX/XXXXX:8020: try once and fail.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;java.net.NoRouteToHostException: No route to host&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Few informations :&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hadoop version : 2.7.3&lt;/P&gt;&lt;P&gt;dfs.client.retry.policy.enabled :&amp;nbsp;false&lt;/P&gt;&lt;P&gt;dfs.client.failover.sleep.max.millis :&amp;nbsp;15000&lt;/P&gt;&lt;P&gt;ipc.client.connect.timeout :&amp;nbsp;20000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help !&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 02 Sep 2019 13:42:57 GMT</pubDate>
    <dc:creator>dupuy_gregory</dc:creator>
    <dc:date>2019-09-02T13:42:57Z</dc:date>
  </channel>
</rss>

