hadoop 出现FATAL conf.Configuration: error parsing conf file,异常,hadoopparsing


FATAL conf.Configuration: error parsing conf file: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
14/07/12 23:51:40 ERROR namenode.NameNode: java.lang.RuntimeException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
	at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1235)
	at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1099)
	at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:1045)
	at org.apache.hadoop.conf.Configuration.set(Configuration.java:420)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.setStartupOption(NameNode.java:1320)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1394)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1419)
Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
	at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:684)
	at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:554)
	at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1742)
	at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1416)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2792)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
	at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1148)
	... 6 more
在Hadoop  namenode  -format出现这个异常时一般是由于Hadoop conf目录下面的几个配置文件的编码进行查看,看是否有不正常的编码,以及错误的代码,统一拷贝更改。

hadoop集群配置

你的配置文件mapred-site.xml有问题,估计是哪个配置项写错了,是否可以将此文件内容贴出来看看,最简单的情况下mapred-site.xml的配置如下,一个自定义选项即可,以下是伪分布式或者单机部署配置,分布式将<value>修改为你的jobtracker节点即可。
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>localhost:9001</value>
</property>
</configuration>
 

hadoop 启动前格式化/hadoop namenode -format 出错

检查core-site.xml这个文件是否有缺少标签或者其他什么情况,导致xml解析出错
 

相关内容

    暂无相关文章