Reduce request timeout to 10s from 60s #876
Merged
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.
This value is used to denote the maximum timeout per network request, rather than the overall request. Cosmos SDK's availability resiliency is heavily reliant on failure detection and retries, both within a partition as well as between regions. However, this requires us to not wait indefinitely (which, honestly, 60 seconds is) for a response from the server, and timeout such network calls and let our retry logic kick in.
Hence.. this change decreases the timeout from 60s to 10s.