Fix: 499 errors #61
Merged
Fix: 499 errors #61
Conversation
This file contains hidden or 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
aborted connections had sockets open for 300 seconds which is way too long fixes supabase/infrastructure#1064
default is 50 anyway but exposing in code so that we can fine tune later
darora
approved these changes
Aug 10, 2021
|
🎉 This PR is included in version 0.9.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
when client aborted a request to storage server, it kept the socket open for 300 seconds. S3 SDK couldn't open any more sockets after there were 50 open idle sockets (which is the default).
This PR reduces the socket idle timeout from 300 seconds to 3 seconds and explicitly shows the maxsockets parameter so that it can be finetuned later
fixes https://github.com/supabase/infrastructure/issues/1064