ions.html#s-resource-failure
>>>
>>>
>>> Another option is to set resource stickiness which will stop resources
>>> moving back after a failure:
>>>
>>> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch05s03s02.html
>
et globally in his config.
>>
>>
>> Also note if you are using a two node cluster you will also need the
>> property “no-quorum-policy=ignore” set.
>>
>>
>> This as well.
>>
>>
>> Hope that helps!
>>
>> Cheers,
lso need the property
> “no-quorum-policy=ignore” set.
>
>
> This as well.
>
>
> Hope that helps!
>
> Cheers,
>
> Max
>
>
> From: Daniel Bozeman [mailto:daniel.boze...@americanroamer.com]
> Sent: 17 May 2011 19:09
> To: pacemaker@oss.cluste
t;
> Hope that helps!
>
> Cheers,
>
> Max
>
>
>
> *From:* Daniel Bozeman [mailto:daniel.boze...@americanroamer.com]
> *Sent:* 17 May 2011 19:09
> *To:* pacemaker@oss.clusterlabs.org
> *Subject:* Re: [Pacemaker] Preventing auto-fail-back
>
>
>
> To be more specific
"no-quorum-policy=ignore" set.
Hope that helps!
Cheers,
Max
From: Daniel Bozeman [mailto:daniel.boze...@americanroamer.com]
Sent: 17 May 2011 19:09
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Preventing auto-fail-back
To be more specific:
I've tried following the exam
To be more specific:
I've tried following the example on page 25/26 of this document to the teeth:
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
And it does work as advertised. When I stop corosync, the resource goes to the
other node. I start corosync and it remains there as it shoul
For the life of me, I cannot prevent auto-failback from occurring in a
master-slave setup I have in virtual machines. I have a very simple
configuration:
node $id="4fe75075-333c-4614-8a8a-87149c7c9fbb" ha2 \
attributes standby="off"
node $id="70718968-41b5-4aee-ace1-431b5b65fd52" ha1 \
