<?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: What  are the benefits If I enable Namenoe HA without auto failover vs no namenode HA? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-are-the-benefits-If-I-enable-Namenoe-HA-without-auto/m-p/47757#M43749</link>
    <description>&lt;P&gt;Hi keagles,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It can be still useful to do manual failover in some cases. For example, you would like to do some HW/OS maintenance on the active datanode - you can fail over manually to the other NN without distrupting running processes on the cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, you can do configuration changes to the NN in the same way. Change config, then restart the Standby NN, it will start with the new configuration, fail over, then restart the other one. See, you updated your NN's settings without the need to do a full cluster stop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are not possible with a non-HA configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;zegab&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Nov 2016 22:53:56 GMT</pubDate>
    <dc:creator>zegab</dc:creator>
    <dc:date>2016-11-21T22:53:56Z</dc:date>
    <item>
      <title>What  are the benefits If I enable Namenoe HA without auto failover vs no namenode HA?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-are-the-benefits-If-I-enable-Namenoe-HA-without-auto/m-p/46389#M43748</link>
      <description>&lt;P&gt;It makes perfect sense if we enable auto failover in a NN HA configuration. But if I just want to enable NN HA without enablhing auto failover, does it provide any advantage comparing single namenode + secondary namnode?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: in my non-ha configuration, I have mounted one of my nn dir to NFS by which provides fault tolerance.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2016 23:48:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-are-the-benefits-If-I-enable-Namenoe-HA-without-auto/m-p/46389#M43748</guid>
      <dc:creator>keagles</dc:creator>
      <dc:date>2016-10-17T23:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: What  are the benefits If I enable Namenoe HA without auto failover vs no namenode HA?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-are-the-benefits-If-I-enable-Namenoe-HA-without-auto/m-p/47757#M43749</link>
      <description>&lt;P&gt;Hi keagles,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It can be still useful to do manual failover in some cases. For example, you would like to do some HW/OS maintenance on the active datanode - you can fail over manually to the other NN without distrupting running processes on the cluster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, you can do configuration changes to the NN in the same way. Change config, then restart the Standby NN, it will start with the new configuration, fail over, then restart the other one. See, you updated your NN's settings without the need to do a full cluster stop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are not possible with a non-HA configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;zegab&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2016 22:53:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/What-are-the-benefits-If-I-enable-Namenoe-HA-without-auto/m-p/47757#M43749</guid>
      <dc:creator>zegab</dc:creator>
      <dc:date>2016-11-21T22:53:56Z</dc:date>
    </item>
  </channel>
</rss>

