plugin/health: Don't go lameduck when reloading #5472
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Chris O'Haver cohaver@infoblox.com
1. Why is this pull request needed and what does it do?
When reloading health, don't pause for lameduck duration. Only go into lameduck mode on FinalShutdown.
During a reload, going into lameduck just delays the loading of the new config, and during the lameduck sleep, the old config is still served.
The new function
OnReload
is a copy ofOnFinalShutdown
with the lameduck pause removed.2. Which issues (if any) are related?
Related to #5471
3. Which documentation changes (if any) need to be made?
4. Does this introduce a backward incompatible change or deprecation?