Expert Contributor
Posts: 109
Registered: ‎05-19-2016
Accepted Solution

Replica Not FoundException

[ Edited ]
DatanodeRegistration(, datanodeUuid=5d7a5533-df53-454e-bfb3-2dfcdbfb7b1b, infoPort=50075, infoSecurePort=0, ipcPort=50020, storageInfo=lv=-56;cid=cluster2;nsid=725965767;c=0):Got exception while serving BP-1423177047- to /
org.apache.hadoop.hdfs.server.datanode.ReplicaNotFoundException: Replica not found for BP-1423177047-
	at org.apache.hadoop.hdfs.server.datanode.BlockSender.getReplica(
	at org.apache.hadoop.hdfs.server.datanode.BlockSender.<init>(
	at org.apache.hadoop.hdfs.server.datanode.DataXceiver.readBlock(
	at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.opReadBlock(
	at org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.processOp(


Although my datanodes are working fine I see this error in Diagnostics. Could this be a problem?

Posts: 519
Topics: 14
Kudos: 92
Solutions: 45
Registered: ‎09-02-2016

Re: Replica Not FoundException



I hope you have more than 3 data nodes


Generally there two types of "data missing" issues are possible for many reasons
a. ReplicaNotFoundException
b. BlockMissingException


If your issue is related to BlockMissingException and if you have backup data in your DR environment then you are good otherwise it might be a problem, but for ReplicaNotFoundException, please make sure all your datanodes are healthy and commissioned state. In fact, namenode suppose to handle this automatically whenever a hit occurs on that data.. if not, you can also try hdfs rebalance (or) NN restart may fix this issue, but you don't need to try this option unless some user report any issue on the particular data. In your case no one reported yet and you found it, so you can ignore it for now