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 "Zhe Zhang (JIRA)" <ji...@apache.org> on 2014/08/29 22:13:53 UTC

[jira] [Assigned] (HDFS-5114) getMaxNodesPerRack() in BlockPlacementPolicyDefault does not take decommissioning nodes into account.

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

Zhe Zhang reassigned HDFS-5114:
-------------------------------

    Assignee: Zhe Zhang

> getMaxNodesPerRack() in BlockPlacementPolicyDefault does not take decommissioning nodes into account.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5114
>                 URL: https://issues.apache.org/jira/browse/HDFS-5114
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Kihwal Lee
>            Assignee: Zhe Zhang
>
> If a large proportion of data nodes are being decommissioned, one or more racks may not be writable. However this is not taken into account when the default block placement policy module invokes getMaxNodesPerRack(). Some blocks, especially the ones with a high replication factor, may not be able to fully replicated until those nodes are taken out of dfs.include.  It can actually block decommissioning itself.



--
This message was sent by Atlassian JIRA
(v6.2#6252)