All geek questions in one place

Initialization failed for block pool <register> (Datanode Uuid unassigned)

What is the source of this error and how can it be fixed?

2015-11-29 19:40:04,670 FATAL org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool <registering> (Datanode Uuid unassigned) service to anmol-vm1-new/10.0.1.190:8020. Exiting.
java.io.IOException: All specified directories are not accessible or do not exist.
        at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:217)
        at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:254)
        at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(DataNode.java:974)
        at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(DataNode.java:945)
        at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(BPOfferService.java:278)
        at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(BPServiceActor.java:220)
        at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:816)
        at java.lang.Thread.run(Thread.java:745)
2015-11-29 19:40:04,670 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Ending block pool service for: Block pool <registering> (Datanode Uuid unassigned) service to anmol-vm1-new/10.0.1.190:8020
2015-11-29 19:40:04,771 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Removed Block pool <registering> (Datanode Uuid unassigned)
+4
source share
3 answers

there are 2 possible solutions to solve

First of all:

The cluster ID of the nodes and the data does not match, do not forget to make them the same.

In the node name, change the ur cluster id in the file located in:

$ nano HADOOP_FILE_SYSTEM/namenode/current/VERSION

In the node data, the cluster identifier is stored in the file:

$ nano HADOOP_FILE_SYSTEM/datanode/current/VERSION

Second:

Format namenode:

Hadoop 1.x: $ hadoop namenode -format

Hadoop 2.x: $ hdfs namenode -format
+5
source

I met the same problem and solved it by following these steps:

1. hdfs ( "/tmp/hadoop-root/" )

rm -rf /tmp/hadoop-root/*

2.

bin/hdfs namenode -format

+3

The main reason for this is the datanode and namenode clusterID data type, please unify them with namenode clusterID and then restart hasoop, then it should be enabled.

+1
source

Source: https://habr.com/ru/post/1617911/

More articles:


All Articles