[
https://issues.apache.org/jira/browse/HDFS-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552394#comment-14552394
]
Hudson commented on HDFS-8404:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #2131 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2131/])
HDFS-8404. Pending block replication can get stuck using older genstamp.
Contributed by Nathan Roberts. (kihwal: rev
8860e352c394372e4eb3ebdf82ea899567f34e4e)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestPendingReplication.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
> Pending block replication can get stuck using older genstamp
> ------------------------------------------------------------
>
> Key: HDFS-8404
> URL: https://issues.apache.org/jira/browse/HDFS-8404
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Fix For: 2.7.1
>
> Attachments: HDFS-8404-v0.patch, HDFS-8404-v1.patch
>
>
> If an under-replicated block gets into the pending-replication list, but
> later the genstamp of that block ends up being newer than the one originally
> submitted for replication, the block will fail replication until the NN is
> restarted.
> It will be safer if processPendingReplications() gets up-to-date blockinfo
> before resubmitting replication work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
