Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 18 Apr 2012 20:46:41 +0000 (UTC)
From: "Eli Collins (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1204113125.3232.1334782001569.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-891) DataNode no longer needs to check for
 dfs.network.script
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins updated HDFS-891:
-----------------------------

    Attachment: hdfs-891.txt

Re-uploading the patch to kick jenkins. I think the previous findbugs/audit warning has to do with us removing a System.exit that is referenced in a findbugs excludes file, want to see what the actual warnings are to be sure. Will hold of committing since we may need to update the findbugs file as well.
                
> DataNode no longer needs to check for dfs.network.script
> --------------------------------------------------------
>
>                 Key: HDFS-891
>                 URL: https://issues.apache.org/jira/browse/HDFS-891
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.23.0
>            Reporter: Steve Loughran
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: HDFS-891.patch, hdfs-891.txt
>
>
> Looking at the code for {{DataNode.instantiateDataNode())} , I see that it calls {{system.exit(-1)}} if it is not happy with the configuration
> {code}
>     if (conf.get("dfs.network.script") != null) {
>       LOG.error("This configuration for rack identification is not supported" +
>           " anymore. RackID resolution is handled by the NameNode.");
>       System.exit(-1);
>     }
> {code}
> This is excessive. It should throw an exception and let whoever called the method decide how to handle it. The {{DataNode.main()}} method will log the exception and exit with a -1 value, but other callers (such as anything using {{MiniDFSCluster}} will now see a meaningful message rather than some Junit "tests exited without completing" warning. 
> Easy to write a test for the correct behaviour: start a {{MiniDFSCluster}} with this configuration set, see what happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira