This repository was archived by the owner on Sep 25, 2020. It is now read-only.
introduce max_req_timeout_count #11
Open
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.
Count # of consecutive req_timeout, and if it is too high, mark it as not healthy. If the endpoint is still legit, pinger will bring it back, otherwise if the endpoint is totally down, the endpoint will stay as unhealthy.
This helps us find dead endpoints whose server box is totally down.