hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Templeton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8950) NameNode refresh doesn't remove DataNodes
Date Tue, 25 Aug 2015 22:50:46 GMT

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

Daniel Templeton commented on HDFS-8950:
----------------------------------------

Pulled the patch temporarily while test_patch is running locally.  Will repost with the proper
naming conventions shortly.

> NameNode refresh doesn't remove DataNodes
> -----------------------------------------
>
>                 Key: HDFS-8950
>                 URL: https://issues.apache.org/jira/browse/HDFS-8950
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, namenode
>    Affects Versions: 2.6.0
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> If you remove a DN from NN's allowed host list (HDFS was HA) and then do NN refresh,
it doesn't remove it actually and the NN UI keeps showing that node. It may try to allocate
some blocks to that DN as well during an MR job.  This issue is independent from DN decommission.
> To reproduce:
> 1. Add a DN to dfs_hosts_allow
> 2. Refresh NN
> 3. Start DN. Now NN starts seeing DN.
> 4. Stop DN
> 5. Remove DN from dfs_hosts_allow
> 6. Refresh NN -> NN is still reporting DN as being used by HDFS.
> This is different from decom because there DN is added to exclude list in addition to
being removed from allowed list, and in that case everything works correctly.



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

Mime
View raw message