Shulou(Shulou.com)06/03 Report--

Test environment, due to test requirements, re-format namenode, resulting in datanode can not start normally.

1. Check the datanode log and you can find the error "Initialization failed for Block pool (Datanode Uuid unassigned)"

2018-01-27 20 service to 09 service to 49052 FATAL org.apache.hadoop.hdfs.server.datanode.DataNode: service to (Datanode Uuid unassigned) 192.168.67.104 purl 9000. Exiting.java.io.IOException: All specified directories are failed to load.at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead (DataStorage.java:478) at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage (DataNode.java:1361) at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool (DataNode.java:1326) at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo (BPOfferService.java:317) at org.apache.hadoop.hdfs.server.datanode .BPServiceActor.connectToNNNAndHandler (BPServiceActor.java:223) at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run (BPServiceActor.java:801) at java.lang.Thread.run (Thread.java:745) 2018-01-27 20 BPServiceActor.java:801 09 at java.lang.Thread.run 49056 FATAL org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool (Datanode Uuid unassigned) service to c6705 hand 192.168.67.105 at java.lang.Thread.run 9000. Exiting.java.io.IOException: All specified directories are failed to load.at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead (DataStorage.java:478) at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage (DataNode.java:1361) at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool (DataNode.java:1326) at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo (BPOfferService.java:317) at org.apache.hadoop.hdfs.server.datanode .BPServiceActor.connectToNNNAndHandler (BPServiceActor.java:223) at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run (BPServiceActor.java:801) at java.lang.Thread.run (Thread.java:745) 2018-01-27 20 BPServiceActor.java:801 09purl 49069 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Ending block pool service for: Block pool (Datanode Uuid unassigned) service to c6705and192.168.67.105Race 90002018-01-27 20Rich 0949070 WARN org.apache.hadoop.hdfs.server .datanode.DataNode: Ending block pool service for: Block pool (Datanode Uuid unassigned) service to c6704 Unique 192.168.67.104 service to 90002018-01-27 20 09 Datanode Uuid unassigned 49192 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Removed Block pool (Datanode Uuid unassigned) 2018-01-27 20 20 09 INFO org.apache.hadoop.hdfs.server.datanode.DataNode 51193 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Exiting Datanode2018-01-27 20 09 purl 51204 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 02018-01-27 20Rom 09VR 51208 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: SHUTDOWN_MSG:/***SHUTDOWN_MSG: Shutting down DataNode at c6706.python279.orgUnip 192.168.67.106 * * /

two。 After Baidu, according to the description of the log, the reason is that the clusterID of datanode does not match the clusterID of namenode.

Open the corresponding directories on datanode and namenode in hdfs-site.xml, open the current/VERSION files respectively, and compare them.

3. The VERSION content of namenode is as follows:

[hdfs@c6704 $cat / data/hadoop/hdfs/name/current/VERSION#Sat Jan 27 00:46:30 UTC 2018namespaceID=1148548909clusterID=CID-aedb2e82-77f2-4056-b676-dca88083215dcTime=0storageType=NAME_NODEblockpoolID=BP-1099214307-192.168.67.104-1517013990445layoutVersion=-63

4. The VERSION file of datanode is as follows:

[hdfs@c6706] $cat / data/hadoop/hdfs/data/current/VERSION#Sat Jan 27 00:20:21 UTC 2018storageID=DS-8f0fdd04-e967-43cd-bd41-93b826b675b8clusterID=CID-b27ecfd8-64ba-4e43-bd82-4ef6f2edd60ccTime=0datanodeUuid=264b1b43-82c0-411c-859f-32761edc7465storageType=DATA_NODElayoutVersion=-565. Namenode and datano

The version of de is different, decide to back up the datanode, empty the VERSION, and then start datanode, the problem remains. Check the VERSION, the content is empty.

[hdfs@c6706 current] $cp VERSION VERSION.bk [hdfs@c6706 current] $echo > VERSION [hdfs@c6706 current] $cat VERSION

6. Delete the VERSION and start the datanode,VERSION content again.

$cat VERSION#Sun Jan 28 01:29:46 UTC 2018storageID=DS-1c1f5e05-df2c-40de-b39b-d6d54e3c4894clusterID=CID-aedb2e82-77f2-4056-b676-dca88083215d # #

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.