hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-5983) Namenode shouldn't read mapred-site.xml
Date Thu, 24 Mar 2011 15:28:05 GMT

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

Rajiv Chittajallu commented on HADOOP-5983:
-------------------------------------------

It probably might have been fixed in trunk. 

I still see this on our Y! internal 0.20.2xx branch. But this has been existed for a while
and should be the same for a Apache Hadoop 0.20 release.

$ xmllint /conf/hadoop/namenode/mapred-site.xml

/conf/hadoop/namenode/mapred-site.xml:615: parser error : Opening and ending tag mismatch:
foobar line 12 and configuration
</configuration>
                ^
/grid/0/gs/conf/hadoop/namenode/mapred-site.xml:616: parser error : Premature end of data
in tag configuration line 6


..

2011-03-24 15:16:26,413 FATAL org.apache.hadoop.conf.Configuration: error parsing conf file:
org.xml.sax.SAXParseException: The element type "foobar" must be terminated by the matching
end-tag "</foobar>".
2011-03-24 15:16:26,413 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.lang.RuntimeException:
org.xml.sax.SAXParseException: The element type "foobar" must be terminated by the matching
end-tag "</foobar>".
	at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1236)
	at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1092)
	at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:1036)
	at org.apache.hadoop.conf.Configuration.get(Configuration.java:414)
	at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:519)
	at org.apache.hadoop.security.Groups.<init>(Groups.java:55)
	at org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:137)
	at org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:180)
	at org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:206)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:241)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:434)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1153)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1162)
Caused by: org.xml.sax.SAXParseException: The element type "foobar" must be terminated by
the matching end-tag "</foobar>".
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:239)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
	at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1141)
	... 12 more

2011-03-24 15:16:26,414 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG:



> 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.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

Mime
View raw message