[
https://issues.apache.org/jira/browse/HDFS-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061441#comment-14061441
]
Hudson commented on HDFS-6678:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #5880 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5880/])
HDFS-6678. MiniDFSCluster may still be partially running after initialization
fails. Contributed by Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1610549)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/MiniDFSCluster.java
> 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
> Fix For: 3.0.0, 2.6.0
>
> 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)
