<?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: Minimum failover time for SGLX in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755694#M57069</link>
    <description>I do not believe that you will be able to get a 12 second failover time. Without the fast failover product which is available on HP-UX but not for Linux, with a 2 second node timeout you would expect around a 30 second failover time. If you reduce the node timeout to 1 second and have a 0.5 second heartbeat interval you can roughly halve this but I would think that puts your cluster at too much risk of transient problems resulting in false failovers.&lt;BR /&gt;&lt;BR /&gt;And of course these times are simply the Serviceguard failover times and do not take into account any application startup or recovery which would be needed after Serviceguard failsover and starts the applicaitons on an adoptive node.</description>
    <pubDate>Wed, 22 Mar 2006 04:15:28 GMT</pubDate>
    <dc:creator>John Bigg</dc:creator>
    <dc:date>2006-03-22T04:15:28Z</dc:date>
    <item>
      <title>Minimum failover time for SGLX</title>
      <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755691#M57066</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;How can i determine The minimum failover time i can get - when a member fail or when a pkg fail?  ( including the time its take to find hardware failare. )&lt;BR /&gt;&lt;BR /&gt;its very simple application - start in notime&amp;amp;&lt;BR /&gt;killed in notime. ( almost)&lt;BR /&gt;&lt;BR /&gt;I need 12 sec. for failover. Is it A &lt;BR /&gt;reasonable request??&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Mar 2006 07:56:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755691#M57066</guid>
      <dc:creator>klemerS</dc:creator>
      <dc:date>2006-03-21T07:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum failover time for SGLX</title>
      <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755692#M57067</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;It is reasonable for most software, though oracle may give you trouble, since it often takes more than 12 seconds for an oracle instance to get started up.&lt;BR /&gt;&lt;BR /&gt;You need to test this to be certain.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 21 Mar 2006 08:24:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755692#M57067</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-21T08:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum failover time for SGLX</title>
      <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755693#M57068</link>
      <description>One thing to be aware of is that the failover time of a Serviceguard package can be determined and controlled by the various parameters, but the point to stress here is that it only makes the time taken to START the package deterministic. What is difficult to give a time for is the actual startup time of the application in the package, as this can be influenced by far too many factors, not least of which is roll forward or roll back of transactions for example.&lt;BR /&gt;So although you could configure for a time of 12 seconds from failure to the package start BEGINNING, you cannot realistically configure for a time whereby the application is up and ready (i.e. the package start has completed) for any and all scenarios&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Mar 2006 12:10:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755693#M57068</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2006-03-21T12:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum failover time for SGLX</title>
      <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755694#M57069</link>
      <description>I do not believe that you will be able to get a 12 second failover time. Without the fast failover product which is available on HP-UX but not for Linux, with a 2 second node timeout you would expect around a 30 second failover time. If you reduce the node timeout to 1 second and have a 0.5 second heartbeat interval you can roughly halve this but I would think that puts your cluster at too much risk of transient problems resulting in false failovers.&lt;BR /&gt;&lt;BR /&gt;And of course these times are simply the Serviceguard failover times and do not take into account any application startup or recovery which would be needed after Serviceguard failsover and starts the applicaitons on an adoptive node.</description>
      <pubDate>Wed, 22 Mar 2006 04:15:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755694#M57069</guid>
      <dc:creator>John Bigg</dc:creator>
      <dc:date>2006-03-22T04:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum failover time for SGLX</title>
      <link>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755695#M57070</link>
      <description>Thanks for your replays.&lt;BR /&gt;&lt;BR /&gt;I also think that 28 sec is the min i can get with QS &amp;amp; 56 sec with lock lun. I will&lt;BR /&gt;&lt;BR /&gt;check it today.</description>
      <pubDate>Thu, 23 Mar 2006 02:59:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/minimum-failover-time-for-sglx/m-p/3755695#M57070</guid>
      <dc:creator>klemerS</dc:creator>
      <dc:date>2006-03-23T02:59:02Z</dc:date>
    </item>
  </channel>
</rss>

