[
https://issues.apache.org/jira/browse/HDFS-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137239#comment-14137239
]
Hudson commented on HDFS-6965:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1899 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1899/])
HDFS-6965. NN continues to issue block locations for DNs with full (kihwal: rev
0c26412be4b3ec40130b7200506c957f0402ecbc)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestBlockManager.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockPlacementPolicyDefault.java
> NN continues to issue block locations for DNs with full disks
> -------------------------------------------------------------
>
> Key: HDFS-6965
> URL: https://issues.apache.org/jira/browse/HDFS-6965
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Rushabh S Shah
> Fix For: 2.6.0
>
> Attachments: HDFS-6965.patch
>
>
> Encountered issues where DNs have less space than a full block and reject
> incoming transfers. The NN continues giving out locations for these nodes
> for some period of time. It does not appear to be related to the DN's cached
> disk usage.
> One impact is required replications are delayed when a full DN is chosen for
> the pipeline. A DN cannot report a broken pipeline so the replication must
> timeout (5m) before new targets are chosen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
