[ClusterLabs] failure-timeout not working in corosync 2.0.1

[Reid Wahl]

Maybe Pacemaker-1 was looser in its handling of resource meta attributes vs
operation meta attributes. Good question.

On Wednesday, March 31, 2021, Antony Stone <Antony.Stone at ha.open.source.it>
wrote:
> On Wednesday 31 March 2021 at 22:53:53, Reid Wahl wrote:
>
>> Hi, Antony. failure-timeout should be a resource meta attribute, not an
>> attribute of the monitor operation. At least I'm not aware of it being
>> configurable per-operation -- maybe it is. Can't check at the moment :)
>
> Okay, I'll try moving it - but that still leaves me wondering why it
works fine
> in pacemaker 1.1.16 and not in 2.0.1.
>
>
> Antony.
>
> --
> Python is executable pseudocode.
> Perl is executable line noise.
>
>                                                    Please reply to the
list;
>                                                          please *don't*
CC me.
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
>

-- 
Regards,

Reid Wahl, RHCA
Senior Software Maintenance Engineer, Red Hat
CEE - Platform Support Delivery - ClusterHA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20210331/bd970d5c/attachment-0001.htm>