-
Notifications
You must be signed in to change notification settings - Fork 3k
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
feat(throttle): extend throttling to API requests #11325
feat(throttle): extend throttling to API requests #11325
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
bb5ad7e
to
3c431a1
Compare
This does not handle the case with multiple GMS instances when MANUAL throttle is toggled. The kafka related throttling works fine since it monitors the same topic lag. However this PR should be updated so that the MANUAL throttle will work across GMS instances when multiple replicas are present. |
84fc9fd
to
8ed172f
Compare
8ed172f
to
7402ff2
Compare
|
||
@Bean | ||
@ConditionalOnProperty(name = "searchService.cacheImplementation", havingValue = "hazelcast") | ||
public ReplicatedMapConfig distributedThrottleMapConfig() { |
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.
Nice, this probably makes sense because it has higher frequency of updates and tighter latency constraints with a low memory footprint.
Ingestion Throttling Update
RETRY_AFTER
http header added for (OpenAPI, Graphql)Checklist