hadoop2.6.0在格式化时异常,启动失败

问题描述

求各位帮看看,本人自学hadoop,在搭建时出现了问题,各种查也没弄明白,求助,希望好心人能留下QQ,进行详聊[zhm@Masterhadoop-2.6.0]$./bin/hdfsnamenode-format15/11/2103:33:27INFOnamenode.NameNode:STARTUP_MSG:/************************************************************STARTUP_MSG:StartingNameNodeSTARTUP_MSG:host=Master.Hadoop/10.171.19.68STARTUP_MSG:args=[-format]STARTUP_MSG:version=2.6.0STARTUP_MSG:classpath=/home/zhm/hadoop/hadoop-2.6.0/etc/hadoop:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-lang-2.6.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-collections-3.2.1.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/stax-api-1.0-2.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/gson-2.2.4.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/paranamer-2.3.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/apacheds-kerberos-codec-2.0.0-M15.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/protobuf-java-2.5.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jersey-server-1.9.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-codec-1.4.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jackson-jaxrs-1.9.13.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jets3t-0.9.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/guava-11.0.2.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/apacheds-i18n-2.0.0-M15.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/httpclient-4.2.5.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jackson-mapper-asl-1.9.13.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-el-1.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/mockito-all-1.8.5.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/api-util-1.0.0-M20.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-beanutils-1.7.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/hadoop-auth-2.6.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-io-2.4.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jasper-compiler-5.5.23.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jersey-json-1.9.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/hadoop-annotations-2.6.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/htrace-core-3.0.4.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jettison-1.1.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/curator-recipes-2.6.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/hamcrest-core-1.3.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-math3-3.1.1.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jackson-xc-1.9.13.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/httpcore-4.2.5.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/xz-1.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/jasper-runtime-5.5.23.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-net-3.1.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/commons-compress-1.4.1.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/curator-client-2.6.0.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/junit-4.11.jar:/home/zhm/hadoop/hadoop-2.6.0/share/hadoop/common/lib/slf4j-api-1.7.5.jar:STARTUP_MSG:build=Unknown-rUnknown;compiledby'root'on2014-12-23T03:59ZSTARTUP_MSG:java=1.8.0_65************************************************************/15/11/2103:33:27INFOnamenode.NameNode:registeredUNIXsignalhandlersfor[TERM,HUP,INT]15/11/2103:33:27INFOnamenode.NameNode:createNameNode[-format]Formattingusingclusterid:CID-d128a1bd-c057-4749-bb58-b7511d4cfc9c15/11/2103:33:28INFOnamenode.FSNamesystem:NoKeyProviderfound.15/11/2103:33:28INFOnamenode.FSNamesystem:fsLockisfair:true15/11/2103:33:28INFOblockmanagement.DatanodeManager:dfs.block.invalidate.limit=100015/11/2103:33:28INFOblockmanagement.DatanodeManager:dfs.namenode.datanode.registration.ip-hostname-check=true15/11/2103:33:28INFOblockmanagement.BlockManager:dfs.namenode.startup.delay.block.deletion.secissetto000:00:00:00.00015/11/2103:33:28INFOblockmanagement.BlockManager:Theblockdeletionwillstartaround2015Nov2103:33:2815/11/2103:33:28INFOutil.GSet:ComputingcapacityformapBlocksMap15/11/2103:33:28INFOutil.GSet:VMtype=64-bit15/11/2103:33:28INFOutil.GSet:2.0%maxmemory966.7MB=19.3MB15/11/2103:33:28INFOutil.GSet:capacity=2^21=2097152entries15/11/2103:33:28INFOblockmanagement.BlockManager:dfs.block.access.token.enable=false15/11/2103:33:28INFOblockmanagement.BlockManager:defaultReplication=215/11/2103:33:28INFOblockmanagement.BlockManager:maxReplication=51215/11/2103:33:28INFOblockmanagement.BlockManager:minReplication=115/11/2103:33:28INFOblockmanagement.BlockManager:maxReplicationStreams=215/11/2103:33:28INFOblockmanagement.BlockManager:shouldCheckForEnoughRacks=false15/11/2103:33:28INFOblockmanagement.BlockManager:replicationRecheckInterval=300015/11/2103:33:28INFOblockmanagement.BlockManager:encryptDataTransfer=false15/11/2103:33:28INFOblockmanagement.BlockManager:maxNumBlocksToLog=100015/11/2103:33:28INFOnamenode.FSNamesystem:fsOwner=zhm(auth:SIMPLE)15/11/2103:33:28INFOnamenode.FSNamesystem:supergroup=supergroup15/11/2103:33:28INFOnamenode.FSNamesystem:isPermissionEnabled=true15/11/2103:33:28INFOnamenode.FSNamesystem:HAEnabled:false15/11/2103:33:28INFOnamenode.FSNamesystem:AppendEnabled:true15/11/2103:33:29INFOutil.GSet:ComputingcapacityformapINodeMap15/11/2103:33:29INFOutil.GSet:VMtype=64-bit15/11/2103:33:29INFOutil.GSet:1.0%maxmemory966.7MB=9.7MB15/11/2103:33:29INFOutil.GSet:capacity=2^20=1048576entries15/11/2103:33:29INFOnamenode.NameNode:Cachingfilenamesoccuringmorethan10times15/11/2103:33:29INFOutil.GSet:ComputingcapacityformapcachedBlocks15/11/2103:33:29INFOutil.GSet:VMtype=64-bit15/11/2103:33:29INFOutil.GSet:0.25%maxmemory966.7MB=2.4MB15/11/2103:33:29INFOutil.GSet:capacity=2^18=262144entries15/11/2103:33:29INFOnamenode.FSNamesystem:dfs.namenode.safemode.threshold-pct=0.999000012874603315/11/2103:33:29INFOnamenode.FSNamesystem:dfs.namenode.safemode.min.datanodes=015/11/2103:33:29INFOnamenode.FSNamesystem:dfs.namenode.safemode.extension=3000015/11/2103:33:29INFOnamenode.FSNamesystem:Retrycacheonnamenodeisenabled15/11/2103:33:29INFOnamenode.FSNamesystem:Retrycachewilluse0.03oftotalheapandretrycacheentryexpirytimeis600000millis15/11/2103:33:29INFOutil.GSet:ComputingcapacityformapNameNodeRetryCache15/11/2103:33:29INFOutil.GSet:VMtype=64-bit15/11/2103:33:29INFOutil.GSet:0.029999999329447746%maxmemory966.7MB=297.0KB15/11/2103:33:29INFOutil.GSet:capacity=2^15=32768entries15/11/2103:33:29INFOnamenode.NNConf:ACLsenabled?false15/11/2103:33:29INFOnamenode.NNConf:XAttrsenabled?true15/11/2103:33:29INFOnamenode.NNConf:Maximumsizeofanxattr:1638415/11/2103:33:29INFOnamenode.FSImage:AllocatednewBlockPoolId:BP-631693077-10.171.19.68-144804800930915/11/2103:33:29WARNnamenode.NameNode:Encounteredexceptionduringformat:java.io.IOException:Cannotcreatedirectory/mnt/tmp/dfs/name/currentatorg.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:337)atorg.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:548)atorg.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:569)atorg.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:148)atorg.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:941)atorg.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379)atorg.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)15/11/2103:33:29FATALnamenode.NameNode:Failedtostartnamenode.java.io.IOException:Cannotcreatedirectory/mnt/tmp/dfs/name/currentatorg.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:337)atorg.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:548)atorg.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:569)atorg.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:148)atorg.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:941)atorg.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379)atorg.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)15/11/2103:33:29INFOutil.ExitUtil:Exitingwithstatus115/11/2103:33:29INFOnamenode.NameNode:SHUTDOWN_MSG:/************************************************************SHUTDOWN_MSG:ShuttingdownNameNodeatMaster.Hadoop/10.171.19.68************************************************************/

解决方案

时间: 2025-01-01 15:35:16

hadoop2.6.0在格式化时异常,启动失败的相关文章

java-JAVA:tamcat启动时异常!!!!!

问题描述 JAVA:tamcat启动时异常!!!!! 我在启动tamcat时 输入startup后 窗口一闪而过.下面是我的启动过程:最后出现的那个异常说是未捕捉到什么? D:tomcat5.5.17bin> startup Using CATALINA_BASE: "D:tomcat5.5.17" Using CATALINA_HOME: "D:tomcat5.5.17" Using CATALINA_TMPDIR: "D:tomcat5.5.17

启动jetty时异常(jetty7+eclipse-indigo+maven3)

问题描述 启动jetty时异常(jetty7+eclipse-indigo+maven3)使用:Eclipse Jetty Launcher Site - http://eclipse-jetty.sourceforge.net/update/ 集成jetty7异常如下:Launching Jetty with port 8080, context / and webapp path src/main/webappException in thread "main" java.lang

hadoop2.2.0+hbase0.96.2启动hbase后无法启动hmaster和hregionserver

问题描述 2014年08月17日星期日23:02:19CSTStoppinghbase(viamaster)2014年08月17日星期日23:02:36CSTStartingmasteronding1corefilesize(blocks,-c)0datasegsize(kbytes,-d)unlimitedschedulingpriority(-e)0filesize(blocks,-f)unlimitedpendingsignals(-i)7889maxlockedmemory(kbytes

hadoop2.7.0 统计字符数量,报“The auxService:mapreduce_shuffle does not exist”异常

问题描述 下面内容是我执行命令输出的内容:-----------------------------------------------------------------------------[root@ikaixin01hadoop-2.7.0]#hadoopjar/cloud/hadoop-2.7.0/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.0.jarwordcount/words/countJavaHotSpot(TM)

Hadoop-2.8.0集群搭建、hadoop源码编译和安装、host配置、ssh免密登录、hadoop配置文件中的参数配置参数总结、hadoop集群测试,安装过程中的常见错误

25.集群搭建 25.1 HADOOP集群搭建 25.1.1集群简介 HADOOP集群具体来说包含两个集群:HDFS集群和YARN集群,两者逻辑上分离,但物理上常在一起 HDFS集群: 负责海量数据的存储,集群中的角色主要有NameNode / DataNode YARN集群: 负责海量数据运算时的资源调度,集群中的角色主要有 ResourceManager /NodeManager 25.1.2服务器准备 本案例使用虚拟机服务器来搭建HADOOP集群,所用软件及版本: ü Vmware 11.

Linux下Hadoop2.6.0集群环境的搭建

本文旨在提供最基本的,可以用于在生产环境进行Hadoop.HDFS分布式环境的搭建,对自己是个总结和整理,也能方便新人学习使用. 基础环境 JDK的安装与配置 现在直接到Oracle官网(http://www.oracle.com/)寻找JDK7的安装包不太容易,因为现在官方推荐JDK8.找了半天才找到JDK下载列表页的地址(http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html).因

国内最全最详细的Hadoop2.2.0集群的HA高可靠的最简单配置

简介 Hadoop中的NameNode好比是人的心脏,非常重要,绝对不可以停止工作.在hadoop1时代,只有一个NameNode.如果该NameNode数据丢失或者不能工作,那么整个集群就不能恢复了.这是hadoop1中的单点问题,也是hadoop1不可靠的表现,如图1所示.hadoop2就解决了这个问题. hadoop2.2.0中HDFS的高可靠指的是可以同时启动2个NameNode.其中一个处于http://www.aliyun.com/zixun/aggregation/7317.htm

Flume1.5.0的安装、部署、简单应用(含伪分布式、与hadoop2.2.0、hbase0.96的案例) … …

------------- 博文作者迦壹 博客地址http://idoall.org/home.php?mod=space&uid=1&do=blog&id=550 转载声明可以转载, 但必须以超链接形式标明文章原始出处和作者信息及版权声明谢谢合作 ------------- 目录 一.什么是Flume? 1)flume的特点 2)flume的可靠性 3)flume的可恢复性 4)flume 的 一些核心概念 二.flume的官方网站在哪里 三.在哪里下载 四.如何安装 五.flu

Hadoop-2.7.0中HDFS NameNode HA实现之DFSZKFailoverController、ZKFailoverController(一)

一.简介       DFSZKFailoverController是Hadoop-2.7.0中HDFS NameNode HA实现的中心组件,它负责整体的故障转移控制等.它是一个守护进程,通过main()方法启动,继承自ZKFailoverController. 二.实现流程       1.启动        通过main()方法启动,如下: /** * 进程启动的main()方法 */ public static void main(String args[]) throws Except