hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nijel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9135) The dfs client will always connect to the old ip which previous resloved after domainname of namenode change to a new ip
Date Fri, 25 Sep 2015 05:48:04 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907629#comment-14907629
] 

nijel commented on HDFS-9135:
-----------------------------

i will look into this. Please feel free to re assign

> 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)

Mime
View raw message