<?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: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81734#M72012</link>
    <description>Hello &lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/18022"&gt;@mbalassi&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;thank you very much for your reply, but I still have some doubts regarding&lt;BR /&gt;this feature. I've just upgraded CDH5.9 to 5.11 and after that I don't see&lt;BR /&gt;any 'previous' directory in Namenodes' Data Directories, neither in&lt;BR /&gt;Datanodes data directories.&lt;BR /&gt;Cloudera's documentation suggests this action is required only if you&lt;BR /&gt;upgrade CDH version 5.0, 5.1 or 5.2:&lt;BR /&gt;&lt;A href="https://www.cloudera.com/documentation/enterprise/5-11-x/PDF/cloudera-upgrade.pdf" target="_blank"&gt;https://www.cloudera.com/documentation/enterprise/5-11-x/PDF/cloudera-upgrade.pdf&lt;/A&gt;&lt;BR /&gt;Similarly -upgradeProgress subcommand is unavailable in hadodp dfsadmin&lt;BR /&gt;command in my current CDH installation. My guess is that Cloudera doesn't&lt;BR /&gt;support this mechanism and keeps it only for compliance with older&lt;BR /&gt;versions. Do you think it's correct assumption?&lt;BR /&gt;</description>
    <pubDate>Wed, 31 Oct 2018 09:55:52 GMT</pubDate>
    <dc:creator>szamasz</dc:creator>
    <dc:date>2018-10-31T09:55:52Z</dc:date>
    <item>
      <title>CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/62382#M72010</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've just finished CDH upgrade with help of Cloudera Manager. Do you know what is the result of 'Finalize Metadata Update' NameNode's option after successful upgrade? I've used this option, but it's still enabled. How can I confirm that upgrade is finalized?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Provided that upgrade is not finalized yet - is there a rollback/downgrade path in case of problems with HDFS? Is it available in any configuration or only if rolling upgrade (HA and Cloudera Enterprise in place) is carried out?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 12:35:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/62382#M72010</guid>
      <dc:creator>szamasz</dc:creator>
      <dc:date>2022-09-16T12:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/80998#M72011</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most likely you have found it out by now, but an easy way is to check whether the NameNode's data directory contains the 'previous' folder in addition to the 'current' folder which is always there during normal operations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also in the newer versions Cloudera Manager gives you a warning when you are running with unfinalized metadata.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 00:07:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/80998#M72011</guid>
      <dc:creator>mbalassi</dc:creator>
      <dc:date>2018-10-11T00:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81734#M72012</link>
      <description>Hello &lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/18022"&gt;@mbalassi&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;thank you very much for your reply, but I still have some doubts regarding&lt;BR /&gt;this feature. I've just upgraded CDH5.9 to 5.11 and after that I don't see&lt;BR /&gt;any 'previous' directory in Namenodes' Data Directories, neither in&lt;BR /&gt;Datanodes data directories.&lt;BR /&gt;Cloudera's documentation suggests this action is required only if you&lt;BR /&gt;upgrade CDH version 5.0, 5.1 or 5.2:&lt;BR /&gt;&lt;A href="https://www.cloudera.com/documentation/enterprise/5-11-x/PDF/cloudera-upgrade.pdf" target="_blank"&gt;https://www.cloudera.com/documentation/enterprise/5-11-x/PDF/cloudera-upgrade.pdf&lt;/A&gt;&lt;BR /&gt;Similarly -upgradeProgress subcommand is unavailable in hadodp dfsadmin&lt;BR /&gt;command in my current CDH installation. My guess is that Cloudera doesn't&lt;BR /&gt;support this mechanism and keeps it only for compliance with older&lt;BR /&gt;versions. Do you think it's correct assumption?&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Oct 2018 09:55:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81734#M72012</guid>
      <dc:creator>szamasz</dc:creator>
      <dc:date>2018-10-31T09:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81736#M72013</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/24582"&gt;@szamasz&lt;/a&gt;, in the case of the 5.9 to 5.11 upgrade you do not see it, because there is no NameNode metadata format change, so there is no need to keep the previous format metadata around (both of those are on HDFS 2.6.0). If you want to see the change you can see it between 5.3 and 5.4 or upgrading to 6.x from 5.x.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The NameNode UI will give you a warning anyway if you have unfinalized metadata changes. If you do not see that you are in the clear. I have just upgraded a cluster from 5.3 to 5.13 and have not finalized the upgrade, can take you a screenshot tomorrow. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Oct 2018 10:30:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81736#M72013</guid>
      <dc:creator>mbalassi</dc:creator>
      <dc:date>2018-10-31T10:30:31Z</dc:date>
    </item>
    <item>
      <title>Re: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81738#M72014</link>
      <description>Wow! That's very informative contribution, thank you for solving one of my&lt;BR /&gt;long lasting questions about CDH. The screenshot will be helpfull too, not&lt;BR /&gt;only for me, but for all community members. Thanks a million!&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Oct 2018 10:45:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81738#M72014</guid>
      <dc:creator>szamasz</dc:creator>
      <dc:date>2018-10-31T10:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: CDH Upgrade - 'Finalize Metadata Upgrade' effect, rollback/downgrade possibilities</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81763#M72015</link>
      <description>&lt;P&gt;The pdf that you are using is deprecated. We are working on removing it from the server. You should only use the current upgrade docs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cloudera.com/documentation/enterprise/upgrade/topics/ug_overview.html" target="_blank"&gt;https://www.cloudera.com/documentation/enterprise/upgrade/topics/ug_overview.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Oct 2018 21:11:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/CDH-Upgrade-Finalize-Metadata-Upgrade-effect-rollback/m-p/81763#M72015</guid>
      <dc:creator>rrielley12</dc:creator>
      <dc:date>2018-10-31T21:11:13Z</dc:date>
    </item>
  </channel>
</rss>

