由于InconsistentFSSStateException导致Hadoop Namenode启动失败

我正在Windows Azure上设置Hadoop（v1.1.1）群集。我试图通过启动NameNode的过程：由于InconsistentFSSStateException导致Hadoop Namenode启动失败

service hadoop-namenode start

但是我始终得到它时，会重新启动被抹了VM关联的下列错误。我移动了这个目录，所以它不会被删除，但它仍然会发生。任何帮助将受到感谢。

STARTUP_MSG: Starting NameNode 
STARTUP_MSG: host = master/10.77.42.61 
STARTUP_MSG: args = [] 
STARTUP_MSG: version = 1.1.1 
STARTUP_MSG: build = https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1.1 -r 1411108; compiled by 'hortonfo' on Mon Nov 19 10:44:13 UTC 2012 
************************************************************/ 
2012-12-13 09:38:54,102 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties 
2012-12-13 09:38:54,222 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source MetricsSystem,sub=Stats registered. 
2012-12-13 09:38:54,230 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 60 second(s). 
2012-12-13 09:38:54,230 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system started 
2012-12-13 09:38:54,675 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source ugi registered. 
2012-12-13 09:38:54,714 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source jvm registered. 
2012-12-13 09:38:54,720 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source NameNode registered. 
2012-12-13 09:38:54,804 INFO org.apache.hadoop.hdfs.util.GSet: VM type  = 64-bit 
2012-12-13 09:38:54,810 INFO org.apache.hadoop.hdfs.util.GSet: 2% max memory = 2.475 MB 
2012-12-13 09:38:54,810 INFO org.apache.hadoop.hdfs.util.GSet: capacity  = 2^18 = 262144 entries 
2012-12-13 09:38:54,810 INFO org.apache.hadoop.hdfs.util.GSet: recommended=262144, actual=262144 
2012-12-13 09:38:54,890 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: fsOwner=hdfs 
2012-12-13 09:38:54,895 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: supergroup=supergroup 
2012-12-13 09:38:54,895 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: isPermissionEnabled=true 
2012-12-13 09:38:54,915 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: dfs.block.invalidate.limit=100 
2012-12-13 09:38:54,915 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: isAccessTokenEnabled=false accessKeyUpdateInterval=0 min(s), accessTokenLifetime=0 min(s) 
2012-12-13 09:38:55,429 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Registered FSNamesystemStateMBean and NameNodeMXBean 
2012-12-13 09:38:55,465 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: Caching file names occuring more than 10 times 
2012-12-13 09:38:55,471 INFO org.apache.hadoop.hdfs.server.common.Storage: Cannot access storage directory /hadoop/name 
2012-12-13 09:38:55,474 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed. 
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /hadoop/name is in an inconsistent state: storage directory does not exist or is not accessible. 
     at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:303) 
     at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:100) 
     at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:411) 
     at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:379) 
     at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:277) 
     at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:529) 
     at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1403) 
     at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1412) 
2012-12-13 09:38:55,476 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /hadoop/name is in an inconsistent state: storage directory does not exist or is not accessible. 
     at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:303) 
     at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:100)

来源

2012-12-13 user1900491

你是否检查了目录上进程的权限？ –

更改目录，您已指定为您的HDFS-site.xml文件的“dfs.name.dir”属性的值，为755和也的权限更改此目录的用户到当前用户.BTW，你能成功格式吗？

来源

2012-12-13 10:25:52 Tariq

我能够如此成功的格式。我在名称文件夹上执行chmod 755，并在运行服务hadoop-namenode start时出现以下错误：ERROR org.apache.hadoop.hdfs.server.namenode.NameNode：java.io.FileNotFoundException：/ hadoop/name/current/VERSION （权限被拒绝）有没有其他想法？ – user1900491

我也以root用户身份工作。 – user1900491

你有没有格式化从根的namenode？ – Tariq

由于InconsistentFSSStateException导致Hadoop Namenode启动失败

回答

相关问题