[Pacemaker] forcing failure on a master (multistate) resource

hj lee kerdosa at gmail.com
Thu Dec 24 14:16:04 EST 2009


On Thu, Dec 17, 2009 at 8:23 AM, Frank DiMeo <Frank.DiMeo at bigbandnet.com>wrote:

>  Hi,
>
>
>
> I need a way to inform the cluster of failures between monitor polls of my
> multistate resources, and I notice that I cannot use “crm_resource “ to
> inform the cluster of the failure of a master (multistate) resource, as it
> seems to only process this function for primitive resources.  I don’t mind
> making the changes to get this to happen, unless there’s some reason why it
> just shouldn’t be done.
>

You can use crm_master command to change the promotion score for master.
Basically the node with higher master score will become master. You can also
use location constraint to prefer the node where you want to run as a
master. The master score = location constraint + promotion score.

Thanks
hj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091224/7220305d/attachment-0003.html>


More information about the Pacemaker mailing list