You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2014/07/14 22:24:05 UTC

[jira] [Commented] (HDFS-6678) MiniDFSCluster may still be partially running after initialization fails.

    [ https://issues.apache.org/jira/browse/HDFS-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061167#comment-14061167 ] 

Andrew Wang commented on HDFS-6678:
-----------------------------------

+1 LGTM

> 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)