[
https://issues.apache.org/jira/browse/HDFS-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061352#comment-14061352
]
Hadoop QA commented on HDFS-6678:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12655601/HDFS-6678.1.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}. There were no new javadoc 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 2.0.3) 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.tools.TestDFSAdminWithHA
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7337//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7337//console
This message is automatically generated.
> MiniDFSCluster may still be partially running after initialization fails.
> -------------------------------------------------------------------------
>
> Key: HDFS-6678
> URL: https://issues.apache.org/jira/browse/HDFS-6678
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HDFS-6678.1.patch
>
>
> {{MiniDFSCluster}} initializes the daemons (NameNodes, DataNodes) as part of
> object construction. If initialization fails, then the constructor throws an
> exception. When this happens, it's possible that daemons are left running in
> the background. There is effectively no way to clean up after this state,
> because the constructor failed, and therefore the caller has no way to
> trigger a shutdown.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
