On Mon, Nov 19, 2012 at 12:55 PM, David Vossel <dvos...@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> 917-418-8423
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
