The latest articles on DEV Community by Lawren (@laurencelin). https://dev.to/laurencelin https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F993261%2F0d914c0d-fa5e-449e-b6c4-e383d17a9a24.png https://dev.to/laurencelin en Lawren Tue, 20 Dec 2022 05:01:28 +0000 https://dev.to/laurencelin/unable-to-start-namenode-with-hadoop-330-on-wsl-2-1c6k https://dev.to/laurencelin/unable-to-start-namenode-with-hadoop-330-on-wsl-2-1c6k <p>I'm running Hadoop on WSL 2, I couldn't open the namenode interface on port 9870I'm using hadoop 3.3.0</p> <p>After checking service with jps, there is only secondary namenode and data node running, while the name node service is gone.</p> <p>Here is my core-site.xml:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>&lt;configuration&gt; &lt;property&gt; &lt;name&gt;fs.defaultFS&lt;/name&gt; &lt;value&gt;hdfs://localhost:9000&lt;/value&gt; &lt;/property&gt; &lt;property&gt; &lt;name&gt;hadoop.tmp.dir&lt;/name&gt; &lt;value&gt;file:/hadoop/hadoop-3.3.0/tmp&lt;/value&gt; &lt;description&gt;&lt;/description&gt; &lt;/property&gt; &lt;/configuration&gt; </code></pre> </div> <p>While running format for namenode, this query showed up:<br> <code>Re-format filesystem in Storage Directory root= /hadoop/hadoop-3.3.0/tmp/dfs/name; location= null ? (Y or N)</code><br> Then I check the log of namenode, it seems unable to read from filepath:<br> <code>org.apache.hadoop.util.ExitUtil: Exiting with status 1: java.io.IOException: Could not parse line: Filesystem 1024-blocks Used Available Capacity Mounted on</code></p> <p>How could I configure the namenode to make it run?<br> Thank you for all the help!</p> gratitude