[Pacemaker] meaning of Monitor Interval

[Lars Marowsky-Bree]

On 2013-09-13T12:20:54, Xiaomin Zhang <zhangxiaomin at gmail.com> wrote:

> Hi, Gurus:
> Here's a question about service Monitor Interval: considering this value is
> configured as '15' seconds, does this mean corosync/pacemaker will take
> average 15 seconds to schedule failed resource on a ready node?

It'll take about a maximum of 15 seconds to schedule a monitoring
operation that can detect the error.

If the monitor operation returns within <1s with a failure, that'll mean
the recovery will begin real quick.

If the monitor operation *doesn't* return but hit it's "timeout" (and is
aborted by the lrmd), then the recovery will be delayed by that much. So
for an ``interval=15 timeout=30'', it could take up to 45s before
recovery is scheduled.

Note however this on timeouts:
http://advogato.org/person/lmb/diary/108.html Just making them shorter
isn't necessarily always beneficial, either.


Best,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde