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 "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2015/12/17 21:03:46 UTC

[jira] [Updated] (HDFS-9515) Avoid calling MiniDFSCluster#shutdown if the cluster was not started successfully

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

Arpit Agarwal updated HDFS-9515:
--------------------------------
    Summary: Avoid calling MiniDFSCluster#shutdown if the cluster was not started successfully  (was: NPE in TestDFSZKFailoverController due to binding exception in MiniDFSCluster.initMiniDFSCluster())

> Avoid calling MiniDFSCluster#shutdown if the cluster was not started successfully
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-9515
>                 URL: https://issues.apache.org/jira/browse/HDFS-9515
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: Jenkins
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Minor
>         Attachments: HDFS-9515.001.patch, HDFS-9515.002.patch, HDFS-9515.003.patch, HDFS-9515.004.patch, HDFS-9515.005.patch
>
>
> If MiniDFSCluster constructor throws an exception, the cluster object is not assigned, so shutdown() call not be called on the object.
> I saw in a recent Jenkins job where binding error threw an exception, and later on the NPE of cluster.shutdown() hid the real cause of the test failure.
> HDFS-9333 has a patch that fixes the bind error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)