On Jan 25, 2008, at 12:22 PM, Hildebrand, Nils, 232 wrote:

Hi,

sigh. Why does everyone reinvent the wheel?


There was a pretty good cluster-software out there (commercial)

who said anything about re-inventing?
"re-implementing" sure, but there aren't exactly many FOSS cluster projects to be borrowing code from.

granted not everything about our implementations are always perfect^, but there's no need to get all preachy about it.


^ you rightly point out the fail-count code, to which I'd reply that we've been planning to do something about it for some time but lack the resources.

which
used the following set of variables for every cluster resource (to be
exact: for every resource type):

- general action timeout
- CI confidence-interval (if online after x seconds clear
failure-counter), CI > (MI + MT) * TL + MI + 10
- first start monitor wait time (in number MIs)
- MT monitor timeout
- number of local restart tries
- number of monitor timeouts before failure
- MI monitor interval
- offline monitor inverval
- offline timeout
- online timeout
- critical (yes/no: if yes, a resource fault will trigger a
resource-group fault)
- TL tolerance limit (how many monitor intervals with result "down" will
it take to declare resource faulted)

This is IMHO the most important subset of attributes which every
resource should have (the mentioned software has some more - but I don't
think these are that important).

This would replace some of the complicated resource-dependency-rules
that are neccessary within heartbeat to emulate the resulting behaviour.

So if you start with timing in lrm - please think about the above.


Kind regards,

Nils


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Beekhof
Sent: Thursday, January 17, 2008 9:13 AM
To: General Linux-HA mailing list
Subject: Re: [Linux-HA] Automatic Clenaup of certain resources


On Jan 17, 2008, at 7:34 AM, Thomas Glanzmann wrote:

Hello,
I use Linux HA to monitor some services on a dial in machine. A so
called single node lcuster. For example sometimes my dial-in
connection or openvpn connection, or IPv6 connectivity does
not come.
Is there a way to tell Linux-HA to retry a failed resource after a
certain amount of time again?

not yet but soon

only in the last few days has the lrmd started exposing the
timing data required in order to do this
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to