-
Notifications
You must be signed in to change notification settings - Fork 974
auth Lua health checks: more responsiveness #16389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…fore. Signed-off-by: Miod Vallat <[email protected]>
Fixes: PowerDNS#16369 Signed-off-by: Miod Vallat <[email protected]>
Pull Request Test Coverage Report for Build 19332892815Details
💛 - Coveralls |
Habbie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved, but please think about the comment i posted
Signed-off-by: Miod Vallat <[email protected]>
|
Logic slightly updated to try and make sure the checker thread, unless awaken earlier to handle new requests, sleeps the same time as before and not a full interval (i.e. takes into account the time it spent processing its queue). This yields a bit more deterministic timings, which the Lua tests are relying upon. |
Short description
The current state of the health check thread is to check for statuses checks to launch, every
lua-health-checks-intervalseconds.This design has two issues:
lua-health-checks-intervalseconds, which will be noticeable if this value is large (as noticed in Lua health checks usually don't trigger after the first resolve but rather wait for lua-health-checks-interval #16369).lua-health-checks-intervalseconds sleep.This PR attempts to address this in two commits:
Checklist
I have: