[
https://issues.apache.org/jira/browse/HDFS-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HDFS-8404:
------------------------------------------
Fix Version/s: 2.6.1
[~sjlee0] backported this to 2.6.1 after fixing minor issues.
I just pushed the commit to 2.6.1 after running compilation and
TestPendingReplication which changed in the patch.
> 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
> Labels: 2.6.1-candidate
> Fix For: 2.6.1, 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)
