On Tue, May 5, 2009 at 5:26 PM, Eliot Gable wrote:
> I have determined that this appears to be something with resource stickiness.
> With the failure-timeout set to 5s, it was timing out the failure and
> switching back to the preferred node so fast that it could not be migrated to
> the other
f Broadvox, LLC.
-Original Message-
From: Andrew Beekhof [mailto:and...@beekhof.net]
Sent: Monday, May 04, 2009 3:39 AM
To: pacemaker@oss.clusterlabs.org
Cc: pacema...@clusterlabs.org
Subject: Re: [Pacemaker] Force a Master resource off a node if another resource
fails
On Fri, May 1, 200
r the use of the individual or
> entity to whom it is addressed. If you are not the intended recipient,
> please call me immediately. BROADVOX is a registered trademark of Broadvox,
> LLC.
>
>
>
> From: Eliot Gable [mailto:ega...@broadvox.net]
> Sent: Thursday, April 30, 2009 5
lease call me
immediately. BROADVOX is a registered trademark of Broadvox, LLC.
From: Eliot Gable [mailto:ega...@broadvox.net]
Sent: Thursday, April 30, 2009 5:58 PM
To: pacema...@clusterlabs.org
Subject: [Pacemaker] Force a Master resource off a node if another resource
fails
Let'
Let's say I have these requirements:
- a master/slave resource called res-a
- a normal resource called res-b that runs on node1 only
- a normal resource called res-c that runs on node2 only
- res-b and res-c both do the same thing, but they are configured as
