<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Replica Not Found errors after CDH 5.3.1-1 upgrade in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Replica-Not-Found-errors-after-CDH-5-3-1-1-upgrade/m-p/24392#M4869</link>
    <description>&lt;P&gt;After upgrading from 5.2.1 to 5.3.1 we are seeing EXT4 errors on our HDFS/Yarm Manager nodes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;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&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 09:21:00 GMT</pubDate>
    <dc:creator>wsanders</dc:creator>
    <dc:date>2022-09-16T09:21:00Z</dc:date>
    <item>
      <title>Replica Not Found errors after CDH 5.3.1-1 upgrade</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Replica-Not-Found-errors-after-CDH-5-3-1-1-upgrade/m-p/24392#M4869</link>
      <description>&lt;P&gt;After upgrading from 5.2.1 to 5.3.1 we are seeing EXT4 errors on our HDFS/Yarm Manager nodes:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;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&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:21:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Replica-Not-Found-errors-after-CDH-5-3-1-1-upgrade/m-p/24392#M4869</guid>
      <dc:creator>wsanders</dc:creator>
      <dc:date>2022-09-16T09:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Replica Not Found errors after CDH 5.3.1-1 upgrade</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Replica-Not-Found-errors-after-CDH-5-3-1-1-upgrade/m-p/24442#M4870</link>
      <description>&lt;P&gt;These errors (in HDFS logs not EXT4 errors in syslog) went away after about an hour.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2015 23:48:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Replica-Not-Found-errors-after-CDH-5-3-1-1-upgrade/m-p/24442#M4870</guid>
      <dc:creator>wsanders</dc:creator>
      <dc:date>2015-02-06T23:48:13Z</dc:date>
    </item>
  </channel>
</rss>

