[ClusterLabs] pacemaker:start-delay

[Andrei Borzenkov]

On Fri, Aug 18, 2023 at 12:13 PM Mr.R via Users <users at clusterlabs.org> wrote:
>
> Hi all，
>
> There is a problem with the start-delay of monitor during the process of
> configuring and starting resources.
>
> For example, there is the result of resource config.
>
> Resource: d1 (class=ocf provider=pacemaker type=Dummy)
>   Meta Attrs: target-role=Stopped
>   Operations: monitor interval=10s start-delay=100s timeout=20s (d1-monitor-interval-10s)
> Resource: d2 (class=ocf provider=pacemaker type=Dummy)
>   Meta Attrs: target-role=Stopped
>   Operations: monitor interval=10s timeout=20s (d2-monitor-interval-10s)
>
> If resource d1 is started first and then resource d2 is started, resource d2 must
> wait for 100s to start. My understanding is  start-delay will not affect the startup of resource d2.
> Is this phenomenon in line with the design expectations? Why design it this way?
>

Each previous state transition must complete before the next state
transition can be initiated. I guess, it is the same as in

https://lists.clusterlabs.org/pipermail/users/2017-October/023060.html