hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6678) MiniDFSCluster may still be partially running after initialization fails.
Date Mon, 14 Jul 2014 19:40:07 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Nauroth updated HDFS-6678:

    Attachment: HDFS-6678.1.patch

The attached patch encloses {{MiniDFSCluster#initMiniDFSCluster}} in a try-finally.  If the
full initialization logic in the try block didn't complete successfully, then the finally
block triggers a shutdown of anything that may have been left running.  The patch looks bigger
than that just because of changes in indentation.

> 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

View raw message