<?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>topic two nodes cluster in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31544#M7477</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In a two-node cluster, epsilon, the value that indicates a node as the master and a requirement in clusters with more than two nodes, is&lt;/P&gt;&lt;P&gt;not held by either node. Instead, both nodes are continuously polled to ensure that if takeover occurs,the node that is still up and running has full read-write access to data as well as access to logical&amp;nbsp; interfaces and management functions. This continuous polling function is referred to as cluster high&lt;/P&gt;&lt;P&gt;availability or cluster HA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Continuously polled &lt;SPAN class="hps"&gt;who can&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;be&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;explained in more detail&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:12:33 GMT</pubDate>
    <dc:creator>wangjundragon</dc:creator>
    <dc:date>2025-06-05T06:12:33Z</dc:date>
    <item>
      <title>two nodes cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31544#M7477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In a two-node cluster, epsilon, the value that indicates a node as the master and a requirement in clusters with more than two nodes, is&lt;/P&gt;&lt;P&gt;not held by either node. Instead, both nodes are continuously polled to ensure that if takeover occurs,the node that is still up and running has full read-write access to data as well as access to logical&amp;nbsp; interfaces and management functions. This continuous polling function is referred to as cluster high&lt;/P&gt;&lt;P&gt;availability or cluster HA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Continuously polled &lt;SPAN class="hps"&gt;who can&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;be&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;explained in more detail&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:12:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31544#M7477</guid>
      <dc:creator>wangjundragon</dc:creator>
      <dc:date>2025-06-05T06:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: two nodes cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31549#M7479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Continuous polling" means that the system will always check that the nodes are up and running. If one node goes down, that node is then considered as the "epsilon" node (though it won't show in cluster show).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The polling takes place on the mailbox disks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2013 14:19:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31549#M7479</guid>
      <dc:creator>parisi</dc:creator>
      <dc:date>2013-01-08T14:19:04Z</dc:date>
    </item>
    <item>
      <title>Re: two nodes cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31553#M7481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to know if the 4-node cluster, a node has gone down, followed by the worst happens,&lt;/P&gt;&lt;P&gt;Another node goes down, It's epsilon node, This time cluster what state is, if node failure recovery, How do I restore the entire state of the cluster normal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 02:17:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31553#M7481</guid>
      <dc:creator>wangjundragon</dc:creator>
      <dc:date>2013-01-09T02:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: two nodes cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31558#M7483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If two nodes in a four node cluster are down and one of the nodes that is down owned epsilon then the next step is to call up NetApp Support with a priority 1 support case. This is because the Vservers in the cluster might not be able to consistently serve data to clients.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 17:50:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31558#M7483</guid>
      <dc:creator>mrinal</dc:creator>
      <dc:date>2013-01-09T17:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: two nodes cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31563#M7485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand that the HA configuration, each node has its own status information in real time is written to the mailbox disk, partner node continues to check whether the mailbox disk information updated mailbox disks of a node is not updated when a certain period of time,that this node has failed, right?&lt;/P&gt;&lt;P&gt;If so, how long is not updated, you will think that this node failure?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 20:26:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/two-nodes-cluster/m-p/31563#M7485</guid>
      <dc:creator>wangjundragon</dc:creator>
      <dc:date>2013-01-09T20:26:21Z</dc:date>
    </item>
  </channel>
</rss>

