[
https://issues.apache.org/jira/browse/HDFS-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544527#comment-14544527
]
Hadoop QA commented on HDFS-8404:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 47s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:red}-1{color} | javac | 1m 35s | The patch appears to cause the
build to fail. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12732974/HDFS-8404-v0.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 09fe16f |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/10988/console |
This message was automatically generated.
> 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
> Attachments: HDFS-8404-v0.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)
