On Fri, Mar 30, 2012 at 8:26 PM, Brian J. Murrell <[email protected]> wrote: > In my cluster configuration, each resource can be run on one of two node > and I designate a "primary" and a "secondary" using location constraints > such as: > > location FOO-primary FOO 20: bar1 > location FOO-secondary FOO 10: bar2 > > And I also set a default stickiness to prevent auto-fail-back (i.e. to > prevent flapping): > > rsc_defaults $id="rsc-options" resource-stickiness="1000" > > This all works as I expect. Resources run where I expect them to while > everything is operating normally and when a node fails the resource > migrates to the secondary and stays there even when the primary node > comes back. > > The question is, what is the proper administrative command(s) to move > the resource back to it's "primary" after I have manually determined > that that node is OK after coming back from a failure? > > I figure I could just create a new resource constraint, wait for the > migration and then remove it, but I just wonder if there is a more > atomic "move back to your preferred node" command I can issue.
crm configure rsc_defaults resource-stickiness=0 ... and then when resources have moved back, set it to 1000 again. It's really that simple. :) Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Pacemaker mailing list: [email protected] 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
