[Pacemaker] unmanaged resource stopped the group

[Andrew Beekhof]

On 24/05/2013, at 5:32 PM, Alexandr A. Alexandrov <shurrman at gmail.com> wrote:

> Hi Andrew,
> 
> 
>> Did you set is-managed=false for the group or a resource in the group?
>> I'm assuming the latter - basically the cluster noticed your resource was not running anymore.
>> While it did not try and do anything to fix that resource, it did stop anything that needed it.
>> Then when the resource came back, it was able to start the dependancies again.
> 
> 
> Yes, i made just one resource in the group unmanaged.
> I assumed/expected that when I make resource unmanaged, the cluster does not take it into account in any operations/dependancies any more. 

Incorrect, it just wont attempt to start or stop it anymore.

> 
> Moreover, here is part of cib settings: pretty complicated dependancies :-) but the point is - I do not understand why I got stopped both WcsGroup and WebGroup resources just because wcs_wcsd resource was stopped/failed?

Hard to say, there is no resource below with is-managed=false

> 
> 
> group IpGroup viplocal vip opensips
> group OraGroup oracle_fs lsnr orcl 
> group WcsGroup wcs_fs wcs_imq wcs_wcsd wasd 
> group WebGroup mysql pgsql nginx nandu tomcat_service 
> ms ms_oracle oracle_drbd \
>         meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" target-role="Master" is-managed="true"
> ms ms_wcs wcs_drbd \
>         meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" target-role="Master" is-managed="true"
> colocation all_in_one inf: IpGroup OraGroup ( WcsGroup WebGroup )
> colocation coloc_ora inf: ms_oracle:Master viplocal
> colocation coloc_ora_fs inf: oracle_fs ms_oracle:Master
> colocation coloc_wcs inf: ms_wcs:Master viplocal
> colocation coloc_wcs_fs inf: wcs_fs ms_wcs:Master
> order order_ora inf: ms_oracle:promote oracle_fs:start lsnr orcl
> order order_ora_after_ip inf: IpGroup OraGroup
> order order_wcs inf: ms_wcs:promote wcs_fs:start wcs_imq wcs_wcsd wasd
> order order_wcs_after_ora inf: OraGroup WcsGroup
> order order_web_after_ora inf: OraGroup WebGroup
> 
> The dependancies in a group come from left to right, don't they? So why I got the whole WcsGroup stopped? And also WebGroup got stopped, while it should not depend on WcsGroup? (colocation all_in_one)
> 
> Best regards,
> Alexandr
> 
> 24.05.2013 07:29, Andrew Beekhof пишет:
>> Did you set is-managed=false for the group or a resource in the group?
>> I'm assuming the latter - basically the cluster noticed your resource was not running anymore.
>> While it did not try and do anything to fix that resource, it did stop anything that needed it.
>> Then when the resource came back, it was able to start the dependancies again.
>> 
>> A better approach would have been to disable the recurring monitor - then the cluster wouldn't have noticed the resource was restarted.
>> Well, unless the dependancies noticed something they needed wasn't there and failed themselves.
> 
> _______________________________________________
> 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://bugs.clusterlabs.org