On Mar 30, 2012, at 2:35 PM, Florian Haas wrote:
> On Fri, Mar 30, 2012 at 8:26 PM, Brian J. Murrell
> wrote:
>>
>> 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
On 12-03-30 02:35 PM, Florian Haas wrote:
>
> crm configure rsc_defaults resource-stickiness=0
>
> ... and then when resources have moved back, set it to 1000 again.
> It's really that simple. :)
That sounds racy. I am changing a parameter which has the potential to
affect the stickiness of all
On Fri, Mar 30, 2012 at 8:26 PM, Brian J. Murrell 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
>
>
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
p
