设置多节点hadoop集群Blockpool ID不匹配

时间:2019-03-29 06:10:31

标签: hadoop hadoop2

在设置多节点hadoop集群时,我遇到了几个问题。 通过不同的Web门户进行正确的设置。出现了一些基本问题
我正在使用 Hadoop 2.8.5 在主从配置中设置2节点集群。
在第一台计算机上,使用hdfs namenode format

格式化namenode

clusterIDBlockpoolID的分配方式如下:

#Fri Mar 29 11:14:41 IST 2019
namespaceID=576041649
clusterID=CID-98480e8d-f7a9-4e1a-8997-400a7aa150c3
cTime=1553838281164
storageType=NAME_NODE
blockpoolID=BP-954411427-x.x.x.y-1553838281164
layoutVersion=-63

现在在第二台计算机上,我运行命令hdfs namenode format -clusterId CID-98480e8d-f7a9-4e1a-8997-400a7aa150c3

#Fri Mar 29 11:15:38 IST 2019
namespaceID=304822257
clusterID=CID-98480e8d-f7a9-4e1a-8997-400a7aa150c3
cTime=1553838338130
storageType=NAME_NODE
blockpoolID=BP-1421744029-x.x.x.x-1553838338130
layoutVersion=-63

考虑到从站和主站应该具有相同的clusterID,如果我错了,请纠正我。 配置似乎正常运行,但是在logs/hadoop-cassandra-datanode-localnosql1.loglogs/hadoop-cassandra-datanode-localnosql2.log的日志中出现错误

2019-03-29 11:25:44,009 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-954411427-x.x.x.y-1553838281164 (Datanode Uuid 4b90bebb-3c34-43d5-8285-6ec6dfefc0a7) service to localnosql1/x.x.x.x:8020 Blockpool ID mismatch: previously connected to Blockpool ID BP-954411427-x.x.x.y-1553838281164 but now connected to Blockpool ID BP-1421744029-x.x.x.x-1553838338130  
2019-03-29 11:25:49,010 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-954411427-x.x.x.y-1553838281164 (Datanode Uuid 4b90bebb-3c34-43d5-8285-6ec6dfefc0a7) service to localnosql1/x.x.x.x:8020 Blockpool ID mismatch: previously connected to Blockpool ID BP-954411427-x.x.x.y-1553838281164 but now connected to Blockpool ID BP-1421744029-x.x.x.x-1553838338130  
2019-03-29 11:25:54,012 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-954411427-x.x.x.y-1553838281164 (Datanode Uuid 4b90bebb-3c34-43d5-8285-6ec6dfefc0a7) service to localnosql1/x.x.x.x:8020 Blockpool ID mismatch: previously connected to Blockpool ID BP-954411427-x.x.x.y-1553838281164 but now connected to Blockpool ID BP-1421744029-x.x.x.x-1553838338130  
2019-03-29 11:25:59,013 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-954411427-x.x.x.y-1553838281164 (Datanode Uuid 4b90bebb-3c34-43d5-8285-6ec6dfefc0a7) service to localnosql1/x.x.x.x:8020 Blockpool ID mismatch: previously connected to Blockpool ID BP-954411427-x.x.x.y-1553838281164 but now connected to Blockpool ID BP-1421744029-x.x.x.x-1553838338130  
2019-03-29 11:26:04,014 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for Block pool BP-954411427-x.x.x.y-1553838281164 (Datanode Uuid 4b90bebb-3c34-43d5-8285-6ec6dfefc0a7) service to localnosql1/x.x.x.x:8020 Blockpool ID mismatch: previously connected to Blockpool ID BP-954411427-x.x.x.y-1553838281164 but now connected to Blockpool ID BP-1421744029-x.x.x.x-1553838338130  

这些错误日志提示了什么?

所有主节点和从节点上的块池ID是否需要与clusterId相同,如果是,该怎么做?

1 个答案:

答案 0 :(得分:1)

为什么要尝试两次格式化namenode?理想情况下,在多节点配置中,有一个名称节点和许多数据节点。 首次设置时,您可以通过“ hdfs namenode -format”初始化namenode,然后启动datanodes,它可以正常工作。

如果您正在尝试多主机配置(多个namenode同时运行),则我不确定它们是否可以正常工作。

如果您要为namenode尝试主备配置,则可以尝试以下步骤

Hadoop Namenode HA setup