On Jan 24, 2008, at 10:20 AM, GAUTIER Hervé wrote:
Hi there !
As Sylvain, I don't understand how HeartBeat (and in particular
PaceMaker) ensure high availability of a service (application
resource) if it is not possible to configure automatic failover in
case of resource failure needed by the service ?
It _does_ do automatic failover.
What it wont do is move to a node where the resource has _already_
failed.
Soon we will be able to do even better than this by using the new LRM
timing data to expire failures automagically (thus allowing a resource
that fails for a second or third time to return to the original node
after a configured interval)
How people configure HB to ensure the service ???
Best regards.
Andrew Beekhof a écrit :
On Jan 24, 2008, at 9:47 AM, Sylvain MALAVIEILLE wrote:
Hello.
Testing Heartbeat v2.1.2 I'm trying to configure failover.
I'm looking for initiate a failover on a failed monitored resource.
I have been doing that unsing the "default-failure-stickiness",
but when the two node scores (computed by heartbeat) are negative
the resource is stopped.
Is there any way to initiate failover indefinitely on resource
failure ?
not unless you put the whole node into standby
and even that wont work if the node you want to move to has a
negative score
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
Hervé GAUTIER
_______________________________________________
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
