[Pacemaker] BUG in master scores: negative master score leads to _stop_ of instance - why?

Lars Ellenberg lars.ellenberg at linbit.com
Thu Oct 1 11:46:58 EDT 2009


On Thu, Oct 01, 2009 at 05:45:30PM +0200, Lars Ellenberg wrote:
> 
> attached is a full cibadmin -Q.

I hate it. grmblf.

> there is exactly one master slave configured,
> primitive is the dummy Stateful agent.
> 
> current cluster state is "stable",
> one Master, one Slave, all well.
> 
> if I now change the master score of the slave to -2 (or -5, or
> -INFINITY), ptest complains about "cannot run anywhere",
> and stopps it!
> (which is also what we see when actually using it,
>  whether with that dummy Stateful RA, or with DRBD).
> 
> I was told to use negative master scores to prevent promotion,
> and I'd like to do so.  But apparently that is a no-go.
> 
> Why would a negative master score cause a slave to be stopped?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Stateful-bug.xml.gz
Type: application/x-gzip
Size: 1717 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091001/0c8a8702/attachment-0001.bin>


More information about the Pacemaker mailing list