Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Users

Heartbeats failover time

 

 

Linux-HA users RSS feed   Index | Next | Previous | View Threaded


lgalea at bluecatnetworks

Sep 18, 2002, 9:03 AM

Post #1 of 3 (345 views)
Permalink
Heartbeats failover time

This is a multi-part message in MIME format.

------_=_NextPart_001_01C25F2C.FFA752CB
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have tried to tweak my HA config files in order to minimize the time
before failover occurs and I cannot seem to get it below about 15
secs...=20
It would be fine to increase the priority of the ha process in order to
prevent premature failover if I could get the time down to a couple
seconds.
Is there any way to achieve this?=20
=20
Thanks in advance
=20
Luke Galea=20
Software Development
BlueCat <http://www.bluecatnetworks.com/> Networks
905-762-5225
=20

------_=_NextPart_001_01C25F2C.FFA752CB
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">




<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml [at] 01C25F0B">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:ApplyBreakingRules/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:UseFELayout/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-alt:\5B8B\4F53;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:SimSun;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:SimSun;}
span.EmailStyle17
{mso-style-type:personal-compose;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:windowtext;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:36.0pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have tried to tweak my HA config files in order to
minimize the time before failover occurs and I cannot seem to get it =
below
about 15 secs&#8230; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It would be fine to increase the priority of <span
class=3DGramE>the ha</span> process in order to prevent premature =
failover if I
could get the time down to a couple =
seconds.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is there any way to achieve this? =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks in advance<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial;mso-no-proof:yes'>Luke Galea =
<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;mso-no-proof:yes'>Software =
Development<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;mso-no-proof:yes'><a =
href=3D"http://www.bluecatnetworks.com/">BlueCat
Networks</a><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;mso-no-proof:yes'>905-762-5225<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C25F2C.FFA752CB--

From Wallwork, Nathan" <nwallwo [at] pnm Wed Sep 18 17:27:03 2002 [5767]
From: Wallwork, Nathan" <nwallwo [at] pnm (Wallwork, Nathan)
Date: Wed, 18 Sep 2002 10:27:03 -0600 (MDT)
Subject: Heartbeats failover time
In-Reply-To: <5DEC3FFCDE2F7C4DA45433EE09A4F22C599FC7 [at] COLOSSUS>
Message-ID: <Pine.LNX.4.44.0209181020241.21333-100000 [at] test0>

On Wed, 18 Sep 2002, Luke Galea wrote:
> I have tried to tweak my HA config files in order to minimize the time
> before failover occurs and I cannot seem to get it below about 15
> secs...
> It would be fine to increase the priority of the ha process in order to
> prevent premature failover if I could get the time down to a couple
> seconds.
> Is there any way to achieve this?

When I was pushing the limits to see what I could get, I set
keepalive 1, deadtime 2, initdead 10, which gave me failover
times of about 8 seconds (I was counting dropped packets for
ongoing one second pings through the heartbeat nodes). I was
using ipfail and inducing a failure by blocking the pings
generated by one of the heartbeat nodes but not the other.

A downside to such a low value for deadtime would be the
potential to mark a node dead due to lost packets if you
get network congestion.


lmb at suse

Sep 18, 2002, 9:09 AM

Post #2 of 3 (322 views)
Permalink
Heartbeats failover time [In reply to]

On 2002-09-18T12:03:59,
Luke Galea <lgalea [at] bluecatnetworks> said:

> I have tried to tweak my HA config files in order to minimize the time
> before failover occurs and I cannot seem to get it below about 15
> secs...

Well, you can certainly set

keepalive 1
deadtime 4
warntime 2

Or something, which should make it possible to failover quite fast. However,
you've to allow time for the STONITH operation etc to complete.

> It would be fine to increase the priority of the ha process in order to
> prevent premature failover if I could get the time down to a couple
> seconds.
> Is there any way to achieve this?

Not without knowing what your goal is ;-)

heartbeat is a good tool to achieve _High_ Availability. It is probably only a
small building block in a system where _continuous_ availability is required;
that we'll require a design somewhat different from a typical fail-over
scenario.


Sincerely,
Lars Marowsky-Brée <lmb [at] suse>

--
Principal Squirrel
Research and Development, SuSE Linux AG

``Immortality is an adequate definition of high availability for me.''
--- Gregory F. Pfister


alanr at unix

Sep 18, 2002, 9:37 AM

Post #3 of 3 (325 views)
Permalink
Heartbeats failover time [In reply to]

Luke Galea wrote:
> I have tried to tweak my HA config files in order to minimize the time
> before failover occurs and I cannot seem to get it below about 15 secs?
>
> It would be fine to increase the priority of the ha process in order to
> prevent premature failover if I could get the time down to a couple seconds.
>
> Is there any way to achieve this?

Heartbeat is already running at real time priority (above all normal user
processes), and it's locked in memory.

What version are you using?

The latest beta has a few minor fixes in the area of realtime performance.
They might help. As always - YMMV.

Do NOT let your system run low on memory.

-- Alan Robertson
alanr [at] unix

Linux-HA users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.