Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 12 Sep 2011 14:34:09 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <862036969.17337.1315838049465.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-5983) Namenode shouldn't read
 mapred-site.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daryn Sharp commented on HADOOP-5983:
-------------------------------------

Unfortunately, no, I'm swamped with other 205 work.  Feel free to take it!  Perhaps you already debugged the issue and know this:
# the mapred-site.xml should not be read in the first place
# the reporter's mapred-site.xml includes local-mapred-site.xml, but the latter file does not exist
# I think the "solutions" are one of:
#- code change: Namenode doesn't include mapred-site.xml, but I very vaguely remember there was problem that made it a non-trivial change
#- user change: Don't have mapred-site.xml include a non-existent local-mapred-site.xml
#- user change: Create local-mapred-site.xml as a blank file

205 has a lot of change as it is, so I'd be hesitant to add another potentially incompatible change when the issue is arguably "user error".  Someone, somewhere, might incorrectly be relying on settings being read from mapred-site.xml that shouldn't be in that file.  I wouldn't make that case for anything but the 20.x line, but I'm by no means going to block the real fix if it's deemed necessary.

> Namenode shouldn't read mapred-site.xml
> ---------------------------------------
>
>                 Key: HADOOP-5983
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5983
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.20.206.0
>            Reporter: Rajiv Chittajallu
>            Assignee: Daryn Sharp
>
> The name node seem to read mapred-site.xml and fails if it can't parse it.
> 2009-06-05 22:37:15,663 FATAL org.apache.hadoop.conf.Configuration: error parsing conf file: org.xml.sax.SAXParseException: Error attempting to parse XML file (href='/hadoop/conf/local/local-mapred-site.xml').
> 2009-06-05 22:37:15,664 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.lang.RuntimeException: org.xml.sax.SAXParseException: Error attempting to parse XML file (href='/hadoop/conf/local/local-mapred-site.xml').
> In our config,  local-mapred-site.xml is included only in mapred-site.xml which we don't push to the namenode.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira