<?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 Re: What is the purpose of running a block report prior to HDP upgrade? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216988#M63812</link>
    <description>&lt;P&gt;Thanks. I hadn't seen the command line upgrade instructions. I agree it's a good idea. In our case, it took nearly 4 hours to get the block report, so I wanted to make sure there was some value in having it.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jun 2017 21:19:50 GMT</pubDate>
    <dc:creator>gholmes</dc:creator>
    <dc:date>2017-06-28T21:19:50Z</dc:date>
    <item>
      <title>What is the purpose of running a block report prior to HDP upgrade?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216986#M63810</link>
      <description>&lt;P&gt;The upgrade instructions call for running a block report to be used later in the process but the docs never mention it again. Why do we run a block report? I know I have no corrupt blocks.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 07:43:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216986#M63810</guid>
      <dc:creator>gholmes</dc:creator>
      <dc:date>2017-06-28T07:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: What is the purpose of running a block report prior to HDP upgrade?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216987#M63811</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/803/gholmes.html" nodeid="803"&gt;@Geoff Holmes&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The block report portion of the pre-upgrade steps is, as you've suspected, to help administrations identify/locate/handle corrupt blocks prior to ugprading and also to validate any namespace issues.  For manual upgrades, there is a step in the docs to manually compare the before and after block reports to identify any issues.  I'm not sure whether Ambari based upgrades do the same check behind the scenes.  It is not a step I would skip though&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.1/bk_command-line-upgrade/content/verify-hdfs-24.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.1/bk_command-line-upgrade/content/verify-hdfs-24.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 20:24:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216987#M63811</guid>
      <dc:creator>ssahi</dc:creator>
      <dc:date>2017-06-28T20:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: What is the purpose of running a block report prior to HDP upgrade?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216988#M63812</link>
      <description>&lt;P&gt;Thanks. I hadn't seen the command line upgrade instructions. I agree it's a good idea. In our case, it took nearly 4 hours to get the block report, so I wanted to make sure there was some value in having it.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 21:19:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-is-the-purpose-of-running-a-block-report-prior-to-HDP/m-p/216988#M63812</guid>
      <dc:creator>gholmes</dc:creator>
      <dc:date>2017-06-28T21:19:50Z</dc:date>
    </item>
  </channel>
</rss>

