[Pacemaker] multistate resource warning

[Lars Ellenberg]

On Wed, Jan 06, 2010 at 09:02:07PM +0100, Lars Ellenberg wrote:
> On Wed, Jan 06, 2010 at 10:52:41AM -0500, Frank DiMeo wrote:
> > When I remove the target-role=master specifier from the configuration,
> > and then put the node where the master resources are running into
> > standby, the resources on the remaining node do not get promoted to
> > the master state.  Only with this specifier included will the slaves
> > be promoted to master in this scenario.  Is that correct?
> 
> clusterlabs.org,
> documentation
> configuration explained
> 10.3.3.6. Which Resource Instance is Promoted
> 
> may help
> 
> just avoid the "other alternative" of location constraints on the
> master role, as explained previously.  or at least use a very low score.

actually, even though it is obvious once you know it,
that paragraph lacks one important bit of information:


if for a given node and resource there is no master score,
or a zero or negative master score, it will not be promoted.

in short, the resource agent must use crm_master appropriately
(after start, on post notify events, possibly on monitor, etc.)
to tell the crm whether or not it would be ok to promote
the respective instance.

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.