Distinguish between request and drain timeouts #64
Conversation
This file contains 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
|
@TomaszSlawski-TomTom thanks for notice that |
|
regression #61 |
|
@TomaszSlawski-TomTom your fix was released, you need to restart all containers in all clusters to apply this Thanks! |
|
@maksim-paskal Thank you for quick merge :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently request timeout is also applied to drain node timeout. This is because request gets child ctx with timeout and the same ctx with timeout is passed to drain logic even if there is separate 120s timeout.
To fix it we have to pass main ctx to drain logic and timeouted one to request.