<?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: How to troubleshoot slow NameNode start up? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/How-to-troubleshoot-slow-NameNode-start-up/m-p/281531#M209427</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/52124"&gt;@Elephanta&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The name node start is usually faster than what you are experiencing frm the logs I am seeing maybe the root cause. During startup the namenode read the fsimage which is the last best cluster images usually a combination of fsimage and the last edits log.&amp;nbsp; You will need to combine the current fsimage and the edits log in the below steps.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="java"&gt;Name node is in safe mode.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the name node is in this state it's a security future that disables any change that the namenode metadata that it can't register,/record to note all the cluster wise location, state, permissions,ownership etc are stored in the metadata which is stored in the name node. You will need to do the following steps as root user while the cluster is freezing during startup.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;# su - hdfs&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Get the current state&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;$ hdfs hdfsadmin -safemode get&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That will confirm that the namenode is in safe mode, you will need to force the creation of a hdfs image point in time by saving the namespace to create a new fsimage&lt;BR /&gt;&lt;STRONG&gt;$ hdfs dfsadmin -saveNamespace&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;confirm safemode is off&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;$ hdfs hdfsadmin -safemode get&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This time the output should be &lt;STRONG&gt;Off&amp;nbsp; &lt;/STRONG&gt;leave safe mode and next time the startup should be much faster&lt;STRONG&gt;&lt;BR /&gt;$ hdfs hdfsadmin -safemode get&lt;BR /&gt;&lt;/STRONG&gt;&lt;SPAN&gt;You might need to tune the memory allocated to the name node it seems the numebr of files to manage has increased hence the need to reconfigure the memory&amp;nbsp; have a look at the below link for guidance..&lt;BR /&gt;&lt;/SPAN&gt;&lt;A href="https://www.ibm.com/support/pages/configuring-namenode-heap-size" target="_blank" rel="noopener"&gt;Configuring NameNode Heap Size&lt;/A&gt;&amp;nbsp;to estimate the memory required for the namenode&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Oct 2019 06:24:42 GMT</pubDate>
    <dc:creator>Shelton</dc:creator>
    <dc:date>2019-10-29T06:24:42Z</dc:date>
  </channel>
</rss>

