您的位置:首页 > Web前端 > Node.js

重启hadoop的namenode报错解决方法

2013-02-17 15:29 316 查看
重启hadoop的namenode一些报错的解决方法

1、提示挂载失败

2013-02-16 15:20:22,057 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed.

org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /mnt/nfs/hadoop/filesystem/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:288)

at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:97)

at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:386)

at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:360)

at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:276)

at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:496)

at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1279)

at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1288)

2013-02-16 15:20:22,059 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /mnt/nfs/hadoop/filesystem/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:288)

at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:97)

at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:386)

at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:360)

at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:276)

at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:496)

at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1279)

at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1288)

解决方法:

mount -t nfs -o rw 172.16.3.188://usr/local/public /mnt/nfs

2、重启hadoop块损坏

WARNING : There are about 8 missing blocks. Please check the log or run fsck.

解决方法:

hadoop fsck /

......................................................................Status: CORRUPT

Total size: 1522487447167 B

Total dirs: 37291

Total files: 48370 (Files currently being written: 7)

Total blocks (validated): 68699 (avg. block size 22161711 B) (Total open file blocks (not validated): 6)

********************************

CORRUPT FILES: 8

MISSING BLOCKS: 8

MISSING SIZE: 7621473 B

CORRUPT BLOCKS: 8

********************************

Minimally replicated blocks: 68691 (99.98836 %)

Over-replicated blocks: 0 (0.0 %)

Under-replicated blocks: 615 (0.89520955 %)

Mis-replicated blocks: 0 (0.0 %)

Default replication factor: 3

Average block replication: 3.026507

Corrupt blocks: 8

Missing replicas: 2460 (1.1831588 %)

Number of data-nodes: 6

Number of racks: 1

FSCK ended at Sat Feb 16 15:58:35 CST 2013 in 2182 milliseconds

The filesystem under path '/' is CORRUPT

3、hbase报错

org.apache.hadoop.hbase.regionserver.HRegionServer:

> NotServingRegionException; Region is not online

解决方法:

run :./hbase hbck
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: