Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A135F9FC1 for ; Mon, 28 Nov 2011 21:52:03 +0000 (UTC) Received: (qmail 49056 invoked by uid 500); 28 Nov 2011 21:52:03 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 49023 invoked by uid 500); 28 Nov 2011 21:52:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 49015 invoked by uid 99); 28 Nov 2011 21:52:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Nov 2011 21:52:03 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Nov 2011 21:52:01 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 1EA44A496D for ; Mon, 28 Nov 2011 21:51:40 +0000 (UTC) Date: Mon, 28 Nov 2011 21:51:40 +0000 (UTC) From: "Hudson (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1011361768.19742.1322517100127.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1133748281.34969.1308871367581.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-7424) Log an error if the topology script doesn't handle multiple args MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158817#comment-13158817 ] Hudson commented on HADOOP-7424: -------------------------------- Integrated in Hadoop-Mapreduce-trunk-Commit #1355 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1355/]) HADOOP-7863: apply HADOOP-7424 to 0.23.1 stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1207614 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt > Log an error if the topology script doesn't handle multiple args > ---------------------------------------------------------------- > > Key: HADOOP-7424 > URL: https://issues.apache.org/jira/browse/HADOOP-7424 > Project: Hadoop Common > Issue Type: Improvement > Reporter: Eli Collins > Assignee: Uma Maheswara Rao G > Labels: newbie > Fix For: 0.24.0 > > Attachments: HADOOP-7424.patch > > > ScriptBasedMapping#resolve currently warns and returns null if it passes n arguments to the topology script and gets back a different number of resolutions. This indicates a bug in the topology script (or it's input) and therefore should be an error. > {code} > // invalid number of entries returned by the script > LOG.warn("Script " + scriptName + " returned " > + Integer.toString(m.size()) + " values when " > + Integer.toString(names.size()) + " were expected."); > return null; > {code} > There's only one place in Hadoop (FSNamesystem init) where we pass multiple arguments to the topology script, and it only done for performance (to trigger resolution/caching of all the hosts in the includes file on startup). So currently a topology script that doesn't handle multiple arguments just means the initial cache population doesn't work. -- 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