<?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 Namenode HA Failure in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Namenode-HA-Failure/m-p/122861#M85614</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I came across a particular issue. &lt;/P&gt;&lt;P&gt;The active NameNode (master01) returned a socket timeout on zkfc, soon after he performed automatically failover bringing master02 to active. But master01 remained in a stalemate, on Ambari NameNode could see up, but without a state (active or stand-by); the process of NameNode on server was up and answered the call. &lt;/P&gt;&lt;P&gt;On NameNode log there are no errors, on zkfc log there are some SocketTimeout (I attached the log). &lt;/P&gt;&lt;P&gt;For resolve this situation we had to restart the NameNode service on the master01, which is automatically left in stand-by just started. &lt;/P&gt;&lt;P&gt;Then I tried to do many manual failover and have positive results all time. On system log no have error, lan is always up and no have error for communicate with server. &lt;/P&gt;&lt;P&gt;As I wrote above, the NameNode service is up and running on all 2 server. &lt;/P&gt;&lt;P&gt;Have an idea of what might have happened? &lt;/P&gt;&lt;P&gt;PS:HDFS service work correctly&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cloudera.com/legacyfs/online/attachments/3843-nn-errors.txt"&gt;nn-errors.txt&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Apr 2016 19:52:12 GMT</pubDate>
    <dc:creator>aubaldi</dc:creator>
    <dc:date>2016-04-29T19:52:12Z</dc:date>
    <item>
      <title>Namenode HA Failure</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Namenode-HA-Failure/m-p/122861#M85614</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I came across a particular issue. &lt;/P&gt;&lt;P&gt;The active NameNode (master01) returned a socket timeout on zkfc, soon after he performed automatically failover bringing master02 to active. But master01 remained in a stalemate, on Ambari NameNode could see up, but without a state (active or stand-by); the process of NameNode on server was up and answered the call. &lt;/P&gt;&lt;P&gt;On NameNode log there are no errors, on zkfc log there are some SocketTimeout (I attached the log). &lt;/P&gt;&lt;P&gt;For resolve this situation we had to restart the NameNode service on the master01, which is automatically left in stand-by just started. &lt;/P&gt;&lt;P&gt;Then I tried to do many manual failover and have positive results all time. On system log no have error, lan is always up and no have error for communicate with server. &lt;/P&gt;&lt;P&gt;As I wrote above, the NameNode service is up and running on all 2 server. &lt;/P&gt;&lt;P&gt;Have an idea of what might have happened? &lt;/P&gt;&lt;P&gt;PS:HDFS service work correctly&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cloudera.com/legacyfs/online/attachments/3843-nn-errors.txt"&gt;nn-errors.txt&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Apr 2016 19:52:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Namenode-HA-Failure/m-p/122861#M85614</guid>
      <dc:creator>aubaldi</dc:creator>
      <dc:date>2016-04-29T19:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: Namenode HA Failure</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Namenode-HA-Failure/m-p/122862#M85615</link>
      <description>&lt;P&gt;It may be &lt;A href="https://issues.apache.org/jira/browse/AMBARI-15235" target="_blank"&gt;https://issues.apache.org/jira/browse/AMBARI-15235&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Apr 2016 20:56:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Namenode-HA-Failure/m-p/122862#M85615</guid>
      <dc:creator>smohanty</dc:creator>
      <dc:date>2016-04-29T20:56:13Z</dc:date>
    </item>
  </channel>
</rss>

