dnsdist: Add an optional status parameter to setAuto()
#5625
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the parameter is present, its value is used to set the initial state of the DownstreamServer until a health check is performed, instead of using the previous known state. It's useful if one wants to restore the automatic status detection but knows that the server is either currently down but was previously up (queries sent until the health check is performed will be lost); or currently up but was previously down, so it process queries immediately.
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Short description
If the parameter is present, its value is used to set the initial state of the
DownstreamServeruntil a health check is performed, instead of using the previous known state.It's useful if one wants to restore the automatic status detection but knows that the server is either currently down but was previously up (queries sent until the health check is performed will be lost); or currently up but was previously down, so it process queries immediately.
Checklist
I have: