[
https://issues.apache.org/jira/browse/HDFS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677255#comment-13677255
]
Hadoop QA commented on HDFS-4887:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12586516/HDFS-4887.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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4486//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4486//console
This message is automatically generated.
> TestNNThroughputBenchmark exits abruptly
> ----------------------------------------
>
> Key: HDFS-4887
> URL: https://issues.apache.org/jira/browse/HDFS-4887
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: benchmarks, test
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-4887.patch
>
>
> After HDFS-4840, TestNNThroughputBenchmark exits in the middle. This is
> because ReplicationMonitor is being stopped while NN is still running.
> This is only valid during testing. In normal cases, ReplicationMonitor thread
> runs all the time once started. In standby or safemode, it just skips
> calculating DN work. I think NNThroughputBenchmark needs to use ExitUtil to
> prevent termination, rather than modifying ReplicationMonitor.
--
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
