[Pacemaker] The placement strategy of the group resource does not work well

[Yuusuke IIDA]

Hi, Yan

After trying your correction , I had the following problems.

   * When trouble happened in a resource below the top of group , it did not 
come in fail over in the node that intended.

I attach crm_report when a problem occurred.

I tried a correction again.

The patch which I attached traces it to a lower resource of group and gets score.

Is there any problem with this correction?

Regards,
Yuusuke

(2011/07/07 21:45), Gao,Yan wrote:
> Hi Yuusuke,
> Thanks a lot for the report and the patch!
>
> I somewhat prefer simplifying the policy, like the attached patch.
>
> What do you think about it? Could you please give it a try?
>
> Regards,
>    Yan
>
>
> On 06/30/11 16:36, Yuusuke IIDA wrote:
>> Hi, Yan
>>
>> I wrote a patch for Pacemaker-dev to solve this problem.
>>
>> I want you to confirm the patch.
>>
>> I want a repository to merge it if there is not a problem.
>>
>> Best Regards,
>> Yuusuke
>>
>> (2011/06/20 16:10), Yuusuke IIDA wrote:
>>> Hi, Yan
>>>
>>> I wanted to scatter transition of the group resource, however failed.
>>>
>>>    * Initial state
>>> Online: [act1 sby1 sby2]
>>> Full list of resources:
>>>    Resource Group: grp1
>>>        rsc1       (ocf::pacemaker:Dummy): Started act1
>>>    Resource Group: grp2
>>>        rsc2       (ocf::pacemaker:Dummy): Started act1
>>>    Resource Group: grp3
>>>        rsc3       (ocf::pacemaker:Dummy): Started act1
>>>
>>>    * When I let you break down in order of grp1 ->   grp2 ->   grp3.
>>> Online: [act1 sby1 sby2]
>>> Full list of resources:
>>>    Resource Group: grp1
>>>        rsc1       (ocf::pacemaker:Dummy): Started sby1
>>>    Resource Group: grp2
>>>        rsc2       (ocf::pacemaker:Dummy): Started sby2
>>>    Resource Group: grp3
>>>        rsc3       (ocf::pacemaker:Dummy): Started sby1
>>>
>>>    * When I let you break down in order of grp3 ->   grp2 ->   grp1. (there is a problem)
>>> Online: [act1 sby1 sby2]
>>> Full list of resources:
>>>    Resource Group: grp1
>>>        rsc1       (ocf::pacemaker:Dummy): Started sby1
>>>    Resource Group: grp2
>>>        rsc2       (ocf::pacemaker:Dummy): Started sby1
>>>    Resource Group: grp3
>>>        rsc3       (ocf::pacemaker:Dummy): Started sby1
>>>
>>> As for this, will not it be right like primitive resource to be dispersed
>>> transition?
>>>
>>> I attach hb_report when a problem happened.
>>>
>>> Best Regards,
>>> Yuusuke
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
----------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: allocate.c.patch
Type: text/x-patch
Size: 1649 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110711/d8641de0/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcmk-Mon-11-Jul-2011.tar.bz2
Type: application/octet-stream
Size: 113930 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110711/d8641de0/attachment-0003.obj>