<?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 Re: clustering doubt in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326554#M877786</link>
    <description>When SystemA - Power fails, then SystemB wont able to receive the heartbeat signals from SysA. Thus, it will succeed in obtaining the clusterlock/quorumdisk which is on a shared disk array b/w SysA and SysB.&lt;BR /&gt;&lt;BR /&gt;-Karthik S S&lt;BR /&gt;&lt;BR /&gt;(Hi there ITRC :-), after a long gap I am back)</description>
    <pubDate>Fri, 09 Jul 2004 12:51:31 GMT</pubDate>
    <dc:creator>Karthik S S</dc:creator>
    <dc:date>2004-07-09T12:51:31Z</dc:date>
    <item>
      <title>clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326549#M877781</link>
      <description>In a two node cluster if the cluster lock is currenrtly locked in systemA and if all of a sudden the power in systemA goes off.then how the systemB will get the cluster lock to reform the cluster.</description>
      <pubDate>Thu, 08 Jul 2004 09:57:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326549#M877781</guid>
      <dc:creator>kamal_9</dc:creator>
      <dc:date>2004-07-08T09:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326550#M877782</link>
      <description>Niether node will lock the cluster lock disk unless it has lost communication with the other node - when that happens, 1 node will get it - the other will TOC.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Thu, 08 Jul 2004 10:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326550#M877782</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-07-08T10:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326551#M877783</link>
      <description>Hi Kamal,&lt;BR /&gt;&lt;BR /&gt;When the cluster is running, cluster lock won't get locked with any of the systems. It's attained only if one system cannot see the other system. If the systemA goes off, then systemB will automatically succeed in obtaining the cluster lock as there is no competition to it. Otherwise whichever the system gets the cluster lock first would take over.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Thu, 08 Jul 2004 10:00:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326551#M877783</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-07-08T10:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326552#M877784</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I do not know what is a cluster lock? is it the quorum disk you are talking about?&lt;BR /&gt;&lt;BR /&gt;manish</description>
      <pubDate>Thu, 08 Jul 2004 10:01:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326552#M877784</guid>
      <dc:creator>Manish Srivastava</dc:creator>
      <dc:date>2004-07-08T10:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326553#M877785</link>
      <description>The cluster lock should be on a drive which is shared between all nodes in the cluster.  One node will always be able to get the lock.</description>
      <pubDate>Fri, 09 Jul 2004 12:26:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326553#M877785</guid>
      <dc:creator>Gary L. Paveza, Jr.</dc:creator>
      <dc:date>2004-07-09T12:26:42Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326554#M877786</link>
      <description>When SystemA - Power fails, then SystemB wont able to receive the heartbeat signals from SysA. Thus, it will succeed in obtaining the clusterlock/quorumdisk which is on a shared disk array b/w SysA and SysB.&lt;BR /&gt;&lt;BR /&gt;-Karthik S S&lt;BR /&gt;&lt;BR /&gt;(Hi there ITRC :-), after a long gap I am back)</description>
      <pubDate>Fri, 09 Jul 2004 12:51:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326554#M877786</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2004-07-09T12:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: clustering doubt</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326555#M877787</link>
      <description>It is not like a system keeps a cluster lock disk locked all the time - it is just used for split of a second when the split brain situation occurs. So if both systemA and systemB are currently part of the cluster, none of them are holding the cluster lock - both the machines are free to lock the disk (for sometime) if the other nodes goes down or there is any communication failure. &lt;BR /&gt;&lt;BR /&gt;In this case, whichever node managed to lock the disk first will form the cluster, the other node can join the cluster if it managed to recover from the failure. If not, the cluster safety timer times out in the other node and it is TOCed.</description>
      <pubDate>Fri, 09 Jul 2004 12:57:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/clustering-doubt/m-p/3326555#M877787</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2004-07-09T12:57:42Z</dc:date>
    </item>
  </channel>
</rss>

