-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fileservice: limit the number of concurrent object storage operations to 100 #17330
Conversation
… to 100 fileservice: set maxConnsPerHost to 100 fileservice: fix http client in AwsSDKv2 fileservice: disable aws sdk client side rate limiter fileservice: add objectStorageSemaphore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the PR description I expect this is a one liner. What the other stuff is doing? Esp why we need a new imp of semaphore?
The MaxConnsPerHost option of the HTTP client doesn't limit the request concurrency, so a true semaphore for the object storage interface is required. |
…s to 100 (matrixorigin#17330) 1000 is too high. Approved by: @fengttt
…s to 100 (matrixorigin#17330) 1000 is too high. Approved by: @fengttt
What type of PR is this?
Which issue(s) this PR fixes:
issue #17329
What this PR does / why we need it:
1000 is too high.