Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this topic

Replica Not Found errors after CDH 5.3.1-1 upgrade

avatar
author-rank wsanders
Explorer

Created on ‎02-05-2015 04:43 PM - edited ‎09-16-2022 02:21 AM

After upgrading from 5.2.1 to 5.3.1 we are seeing EXT4 errors on our HDFS/Yarm Manager nodes:

 

DatanodeRegistration(10.15.129.105, datanodeUuid=d2f178f8-1399-4330-92b9-c627b0a04804, infoPort=50075, ipcPort=50020, storageInfo=lv=-56;cid=cluster15;nsid=601399481;c=0):Got exception while serving BP-447169353-10.15.129.109-1415094554153:blk_1110216188_36477305 to /10.15.129.103:56258
org.apache.hadoop.hdfs.server.datanode.ReplicaNotFoundException: Replica not found for BP-447169353-10.15.129.109-1415094554153:blk_1110216188_36477305

 

The upgrade did not throw any exceptions and "hdfs fsck /" is clean. How can I flush these out of the system? Maybe these are files that did not have time to replicate properly before the upgrade?

2,914
0 Kudos
1
Who agreed with this topic