<?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: NameNode can not be started in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/NameNode-can-not-be-started/m-p/100273#M63292</link>
    <description>&lt;P&gt;Check the size of the file if it is zero bytes then it means there is some corruption with that particular FSImage file. Instead of formatting the namenode which will result in complete data loss, you can just manually remove the FSImage file and then start your namenode with minimal damage to your cluster.&lt;/P&gt;</description>
    <pubDate>Fri, 20 May 2016 18:18:36 GMT</pubDate>
    <dc:creator>abhi_kevin</dc:creator>
    <dc:date>2016-05-20T18:18:36Z</dc:date>
  </channel>
</rss>

