You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "nijel (JIRA)" <ji...@apache.org> on 2015/09/25 07:48:04 UTC

[jira] [Assigned] (HDFS-9135) The dfs client will always connect to the old ip which previous resloved after domainname of namenode change to a new ip

     [ https://issues.apache.org/jira/browse/HDFS-9135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nijel reassigned HDFS-9135:
---------------------------

    Assignee: nijel

> The dfs client will always connect to the old ip which previous resloved after domainname of namenode change to a new ip
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9135
>                 URL: https://issues.apache.org/jira/browse/HDFS-9135
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: liujianhui
>            Assignee: nijel
>            Priority: Minor
>
> when the namenode from one machine to another machine, while the domainname of the namenode is not modify, for example both are namenode.org . now fs.hdfs.impl.disable.cache in conf is false as default, the dfs client will always connect to the old machine firstly, and then connect to the new machine with the IOException reponse. this procedure will waste a few seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)