[Pacemaker] When I started a resource after a stop in the environment that set placement-strategy, there is a problem.

Andrew Beekhof andrew at beekhof.net
Mon Aug 15 02:10:42 EDT 2011


Here you go:
   http://hg.clusterlabs.org/pacemaker/devel/rev/b88e6d03d52f

On Mon, Aug 15, 2011 at 4:01 PM, Yuusuke IIDA
<iidayuus at intellilink.co.jp> wrote:
> Hi, Andrew
>
> Thank you for a reply.
> I wait for a patch.
>
> Regards,
> Yuusuke
>
> (2011/08/11 15:59), Andrew Beekhof wrote:
>>
>> I suspect this function is going to become very similar to
>> sort_clone_instance.
>> I'll commit a slightly more involved patch shortly.  Thanks for
>> pointing out the problem.
>>
>> 2011/8/2 Yuusuke IIDA<iidayuus at intellilink.co.jp>:
>>>
>>> Hi, Yan
>>> Hi, Andrew
>>>
>>> When I operated the resource, I think that I do not want to affect the
>>> irrelevant resource working if possible.
>>>
>>> I performed the following operation in the environment that set
>>> placement-strategy.
>>>
>>>  - I stopped resource grpPostgreSQLDB1 temporarily.
>>>
>>>  - I produced trouble in resource grpPostgreSQLDB3 and moved it to node
>>> act1.
>>>
>>>  - I removed a stop state of resource grpPostgreSQLDB1.
>>>
>>>  - As a result, resource grpPostgreSQLDB1 started in node act2 and
>>> originally
>>> resource grpPostgreSQLDB2 which started in node act2 was thrown out of
>>> the node
>>> and started in node act3.
>>>
>>>  - It is not preferable for service to stop temporarily by starting
>>> resource
>>> grpPostgreSQLDB2 being moved.
>>>
>>> I compare the starting resource with the stopping resource to solve this
>>> problem
>>> and think a resource during the start to have to raise priority.
>>>
>>> I attach a patch to solve this problem.
>>>
>>> Please confirm it.
>>>
>>> Best Regards,
>>> Yuusuke
>>> --
>>> ----------------------------------------
>>> METRO SYSTEMS CO., LTD
>>>
>>> Yuusuke Iida
>>> Mail: iidayuus at intellilink.co.jp
>>> ----------------------------------------
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>>
>>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>
>
> --
> ----------------------------------------
> METRO SYSTEMS CO., LTD
>
> Yuusuke Iida
> Mail: iidayuus at intellilink.co.jp
> ----------------------------------------
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>




More information about the Pacemaker mailing list