Impl. configuration of co-routine request timeouts #116
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
These superseeded the timeouts enacted by the Grizzly server and needed to be configured for concurrent uploads of large files where each request duration exceeded the default of 30 seconds.
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.
Problem
When uploading large files to Kafka concurrently, each request duration exceeds the default timeout of 30 seconds. This causes the service to return 503 http code when thought upload is proceeding correctly.
Solution
This PR implements external configuration of the timeout duration for the REST endpoints. This will allow to configure longer timeout durations on systems where needed.