[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 62318] healthcheck executed more often than configured in hcinterval


--- Comment #3 from Eric Covener <covener@xxxxxxxxx> ---
(In reply to Jim Jagielski from comment #2)
> The issue appears to be one of, mainly, interpretation of what an interval
> is. As seen in the code and the documentation, the value of the interval
> determines when a health check *is performed*. It does not define the time
> *between* health checks, which is a separate timing entirely.
> It is also assumes that the sysadmin matches the interval time with the time
> taken to perform said health check and avoids such nonsense as kicking off a
> check every 100ms if the health check itself takes 250ms.

I don't think increasing the interval helps with a slow health check, since we
check every AP_WD_TM_SLICE to see if a health check has completed in the
desired interval.

If my health check takes 1 second and the interval is 10 seconds, we will still
kick off 10 health checks in rapid succession just after 10 seconds has

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx