<?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/208697#M170654</link>
    <description>&lt;P&gt;Yes, actually it's 20s. I believe that it is the default from the ipc.client.connect.timeout default. I am trying to see if I can set it to 2s. The main problem seems to be that for every FileSystem object I create it wants to always try my server 1 first which is down. It doesn't seem to remember that it was down the last time it tried and continues to keep retrying it for each new FileSystem object. I am also trying caching my own FileSystem object so that, if I reuse an object that has already failed over to the second server, I won't incur the same 2s delay in first trying to connect to the failed server.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2017 23:11:31 GMT</pubDate>
    <dc:creator>kc7bfi</dc:creator>
    <dc:date>2017-10-09T23:11:31Z</dc:date>
  </channel>
</rss>

