[Pacemaker] Upgrading a master salve resource agent, Maintenance best practices

Jesse Hathaway jesse.hathaway at getbraintree.com
Mon Nov 19 14:06:34 EST 2012

On Mon, Nov 19, 2012 at 12:55 PM, David Vossel <dvossel at redhat.com> wrote:

> I do not have much experience managing pacemaker deployments, but this is
> what I would try.
> Set the resource option, is-managed, to false.
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-options.html
> Go in and make whatever changes you need to make to both the cib and the
> active resource. After you are done, set the resource's is-managed option
> back to true, or remove it from the config entirely since the default is
> true.
> Alternatively you could set the entire cluster in maintenance mode by
> setting the cluster option, maintenance-mode, to true. This will
> automatically make all the resources un-managed until maintenance mode is
> turned off again.

Unfortunately, placing the resource or cluster into maintenance mode does
not help, since when the resource is managed again pacemaker notices that
the resource has changed and the policy engine makes any necessary actions,
e.g. in this case restarting the resource.

Jesse Hathaway, Systems Engineer
Braintree <http://getbraintree.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121119/c098d7ac/attachment-0003.html>

More information about the Pacemaker mailing list