<?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: Failed to start secondary namenode in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Failed-to-start-secondary-namenode/m-p/298646#M219297</link>
    <description>&lt;P&gt;Hi Sihi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also encountered similar issue while enabling HA on name-node. We fall into this issue usually because we miss some instructions while enabling HA , like in my case I missed one step to create checkpoint on second NN.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To overcome this thing , please try to start the HA enabling process once again from Ambari UI . And follow every step again correctly. It will again try to create secondary NN and you will be able to bring back the cluster to green state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Arun&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jun 2020 17:14:51 GMT</pubDate>
    <dc:creator>arunek95</dc:creator>
    <dc:date>2020-06-25T17:14:51Z</dc:date>
  </channel>
</rss>

