[9.0] improve service throttling mechanism to reject clients instead of blocking #8323
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
…f blocking The theory is that the connections are still backing up even while the service is sleeping. If we instead close connections agressively during the throttle period hopefully we'll be able to recover from overload periods more effectively
fstagni
approved these changes
Oct 8, 2025
|
Running with this has definitely been better than before, if still not ideal. Fundamentally the DIRAC model of assigning a thread per active RPC call isn't ideal but that isn't going to be fixed. If anyone else struggles with this, increasing the number of threads used by the service seems to have helped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The theory is that the connections are still backing up even while the service is sleeping. If we instead close connections agressively during the throttle period hopefully we'll be able to recover from overload periods more effectively
BEGINRELEASENOTES
*Core
CHANGE: Agressively close connections when serivces are overloaded
For examples look into release.notes
ENDRELEASENOTES