[
https://issues.apache.org/jira/browse/HDFS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710166#comment-13710166
]
Hadoop QA commented on HDFS-4998:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12592585/HDFS-4998.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4662//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4662//console
This message is automatically generated.
> TestUnderReplicatedBlocks fails intermittently
> ----------------------------------------------
>
> Key: HDFS-4998
> URL: https://issues.apache.org/jira/browse/HDFS-4998
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.1.0-beta
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-4998.branch-023.patch, HDFS-4998.trunk.patch
>
>
> Looking at branch-2.1-beta jenkins build, this test case seems flaky.
> First, addToInvalidates() is called against a block on a datanode. This
> removes the dn from the BlockInfo in blocksMap.
> At this point, raising the replication factor can cause the same node to be
> picked. If the node has already deleted the block, it will work. If not, the
> replication fails. When it fails, it will take at least the pending
> replication timeout to reschedule, which is 5 minutes. But the test will
> timeout before this and fail.
> We could make it wait for the completion of actual block deletion. Or the
> test timeout can be made a lot longer, but past jiras against this test case
> indicate people want this to run faster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
