Skip to content

Mark destinations as unhealthy by default #1144

Answered by Tratcher
PieterBoeren asked this question in Q&A
Discussion options

You must be logged in to vote

Destinations currently default to Unknown, but unknown destinations are still considered when routing requests.

Active health checks are triggered immediately upon server startup, you shouldn't have to wait for the 10s interval. However, you're right that there's a time window at startup where requests could be sent to destinations in an unknown state.

There are a few different ways to handling this, but let's start with one question: Since all destinations are in an unknown state at startup until the first active heath checks complete, how do you want to handle incoming requests? Should they be refused with a 503? Should they be paused until the first health checks complete?

Consider thi…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@Tratcher
Comment options

Tratcher Jul 6, 2021
Collaborator

@PieterBoeren
Comment options

@Tratcher
Comment options

Tratcher Jul 6, 2021
Collaborator

Answer selected by karelz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants