[ClusterLabs] Antw: Re: Understanding advisory resource ordering

[Ulrich Windl]

>>> Achim Leitner <aleitner at linux-ag.com> schrieb am 12.01.2020 um 00:28 in
Nachricht <20200111232845.BEA69160B91 at mail.linux-ag.de>:
>>  08.01.2020 17:30, Achim Leitner пишет:
>>> I can't see what is causing this behaviour.
> 
> Am 2020-01-11 17:38, schrieb Andrei Borzenkov:
>> primitive VM-Step8a Delay \
>> 	params startdelay=10 stopdelay=2 mondelay=0 \
>> 	op start interval=0 timeout=40s \
>> 	op stop interval=0 timeout=30s \
>> 	meta target-role=Started
>> primitive VM-Step8b Delay \
>> 	params startdelay=15 stopdelay=2 mondelay=0 \
>> 	op start interval=0 timeout=40s \
>> 	op stop interval=0 timeout=30s \
>> 	meta target-role=Started
>> primitive VM-Step8c Delay \
>> 	params startdelay=5 stopdelay=2 mondelay=0 \
>> 	op start interval=0 timeout=40s \
>> 	op stop interval=0 timeout=30s \
>> 	meta target-role=Started
>> 
>> You know what "startdelay" parameter does, do not you?
> 
> OMG, that's what you get from dozens of attempts to reproduce an issue
> and finally believe you got it - when in fact you got your setting 
> wrong.
> Sorry for the noise. Still, we have seen resources start sequentially in
> the real scenario. Will have to try again to reproduce it.

Don't forget: Resources MAY start in parallel, but they NEED NOT. My guess is
the fster a resource stars, the less likely it is to see parallelism.

Regards,
Ulrich

> 
> Achim Leitner
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/