[
https://issues.apache.org/jira/browse/HDFS-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057036#comment-15057036
]
Hudson commented on HDFS-9535:
------------------------------
ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #692 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/692/])
HDFS-9535. Newly completed blocks in IBR should not be considered (jing9: rev
e53456981474d6e16e3c134e3777b3588dc6fedf)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> Newly completed blocks in IBR should not be considered under-replicated too
> quickly
> -----------------------------------------------------------------------------------
>
> Key: HDFS-9535
> URL: https://issues.apache.org/jira/browse/HDFS-9535
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.8.0
> Reporter: Jing Zhao
> Assignee: Mingliang Liu
> Fix For: 2.8.0
>
> Attachments: HDFS-9535.000.patch, HDFS-9535.001.patch,
> HDFS-9535.002.patch
>
>
> TestReplication#testNoExtraReplicationWhenBlockReceivedIsLate failed in
> several Jenkins run (e.g.,
> https://builds.apache.org/job/PreCommit-HDFS-Build/13818/testReport/). The
> failure is on the last {{assertNoReplicationWasPerformed}} check.
> This test failure reveals a scenario that HDFS-1172 missed: if a block is
> first committed by the client, and then the first IBR comes to the NN, as
> proposed by HDFS-1172, we should still put the remaining expected replicas
> into the pending queue, instead of the under-replicated queue. Please see
> [~liuml07]'s comment
> [here|https://issues.apache.org/jira/browse/HDFS-9535?focusedCommentId=15052397&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15052397]
> for more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
