<?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: Issue : &amp;quot;sandbox-hdp.hortonworks.com:8020 failed on connection exception: java.net.connectexception: connection refused;&amp;quot; for namenode in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Issue-quot-sandbox-hdp-hortonworks-com-8020-failed-on/m-p/268857#M206440</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35813"&gt;@shashank_naresh&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following error can occur if the NameNode is not running fine.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Highlighted Error:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="java"&gt;Call From sandbox-hdp.hortonworks.com/172.18.0.3 to sandbox-hdp.hortonworks.com:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  &amp;lt;a href="http://wiki.apache.org/hadoop/ConnectionRefused" target="_blank"&amp;gt;http://wiki.apache.org/hadoop/ConnectionRefused&amp;lt;/a&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Possible cause:&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;1). Please verify if the port 8020 is actually listening?&amp;nbsp; If not then we will need to check the NameNode log for any errors. We might need to also check the NameNode GC log to see if it has sufficient memory and if the GC is happening properly or not?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# netstat -tnlpa | grep 8020
# netcat -tnlpa | grep 50070&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2). There might be some errors listed in NameNode logs that can be found at. So can you please check and share the log file here?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# ls -l  /var/log/hadoop/hdfs/hadoop-hdfs-namenode-sandbox-hdp.hortonworks.com.log
# ls -lart /var/log/hadoop/hdfs/gc.log-201908*&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Specially in case of Sandbox Environment:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As Sandbox is a single node cluster for testing/learning purpose which has a lots of services running on a single host so some times we might see that due to heavy load of other running services other services like NameNode ..etc does not function properly.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;So please try this:&lt;/STRONG&gt;&amp;nbsp; Stop the services that you are not needing currently in your Sandbox. Put those services in maintenance mode form Ambari UI and then just start the services that you are testing currently.&amp;nbsp; This should free some memory on the sandbox host and back ground processing load by those services and that should improve the scenario.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 24 Aug 2019 21:22:23 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2019-08-24T21:22:23Z</dc:date>
  </channel>
</rss>

