lite-log hadoop hdfs

Hadoop datanode issue and resolution - ‘Incompatible clusterIDs’

286 views 0 comments about 4 months ago Raymond Tang


After finishing installation Hadoop 3.0.0 in my Windows: Install Hadoop 3.0.0 in Windows (Single Node), I got the following error after I formated the name node several times.

The following error is thrown out when I tried to start Hadoop HDFS.

2018-02-19 22:02:06,848 WARN common.Storage: Failed to add storage directory [DISK]file:/F:/DataAnalytics/dfs/data Incompatible clusterIDs in F:\DataAnalytics\dfs\data: namenode clusterID = CID-ef46d03c-27ff-45f3-88ae-a2b6f207b001; datanode clusterID = CID-242a04f8-6b63-4325-b56e-14b608af786c
         at org.apache.hadoop.hdfs.server.datanode.DataStorage.doTransition(
         at org.apache.hadoop.hdfs.server.datanode.DataStorage.loadStorageDirectory(
         at org.apache.hadoop.hdfs.server.datanode.DataStorage.loadDataStorage(
         at org.apache.hadoop.hdfs.server.datanode.DataStorage.addStorageLocations(
         at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(
         at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(
         at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(
         at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(
         at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(
2018-02-19 22:02:06,851 ERROR datanode.DataNode: Initialization failed for Block pool <registering> (Datanode Uuid 94e366db-2ed5-40a2-bc36-7335bfcdec05) service to / Exiting. All specified directories have failed to load.

Root cause

This issue happened because the cluster id in my hadoop name node and data node VERSION files are not consistent.


The root cause is: I formated the namenode using the following command without deleting the files in data node directory:

hadoop namenode -format


Before formarting name node, ensure the files under <>/ directories are deleted on all data nodes.

Add comment

Comments (0)
No comments yet.