hadoop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sidharth Kumar <sidharthkumar2...@gmail.com>
Subject Re: Block pool error in datanode
Date Wed, 24 May 2017 06:07:07 GMT
So I guess this is due to change in blockpool id. If you have older fsimage
backup ,start namenode using that fsimage or delete the current directory
of datanodes hdfs storage and re-format the namenode once again

Regards
Sidharth
Mob: +91 8197555599
LinkedIn: www.linkedin.com/in/sidharthkumar2792

On 23-May-2017 7:52 PM, "Dhanushka Parakrama" <parakrama1282@gmail.com>
wrote:

> Hi All
>
> I have 5 node cluster  where  2 name node are runs in active and standby
> mode . when i try to add the data nodes after name node format i get the
> below error . is there any way to fix it
>
>
>
>
>
> Error
> ====
> 2017-05-23 14:10:29,805 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode:
> Initialization failed for Block pool BP-1938612011-192.168.56.148-1495541823828
> (Datanode Uuid 5c652b07-e0cb-4917-9435-f534a680dbad) service to
> nn2.cluster.com/192.168.56.149:9000 Blockpool ID mismatch: previously
> connected to Blockpool ID BP-1938612011-192.168.56.148-1495541823828 but
> now connected to Blockpool ID BP-769166748-192.168.56.148-1494926203928
> 2017-05-23 14:10:34,808 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode:
> Initialization failed for Block pool BP-1938612011-192.168.56.148-1495541823828
> (Datanode Uuid 5c652b07-e0cb-4917-9435-f534a680dbad) service to
> nn2.cluster.com/192.168.56.149:9000 Blockpool ID mismatch: previously
> connected to Blockpool ID BP-1938612011-192.168.56.148-1495541823828 but
> now connected to Blockpool ID BP-769166748-192.168.56.148-1494926203928
>
>
>
>
>
>

Mime
View raw message