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
Add dynamic config for per instance visibility API rate limit #2585
Add dynamic config for per instance visibility API rate limit #2585
Conversation
can you plz take a look at this example? i believe this might be better |
common/dynamicconfig/constants.go
Outdated
@@ -152,6 +152,8 @@ const ( | |||
FrontendMaxNamespaceBurstPerInstance = "frontend.namespaceBurst" | |||
// FrontendMaxNamespaceCountPerInstance is workflow namespace count limit per second | |||
FrontendMaxNamespaceCountPerInstance = "frontend.namespaceCount" | |||
// FrontendMaxVisibilityNamespaceRPSPerInstance is namespace rate limit per second for visibility APIs | |||
FrontendMaxVisibilityNamespaceRPSPerInstance = "frontend.visibilityNamespaceRPS" |
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.
how about frontend.namespaceRPS.visibility ?
testGetIntPropertyFilteredByNamespaceApiTypeKey: | ||
- value: 30 | ||
constraints: {} | ||
- value: 20 | ||
constraints: | ||
namespace: samples-namespace | ||
- value: 10 | ||
constraints: | ||
namespace: samples-namespace | ||
apiType: visibility |
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.
can you set a default RPS for visibility to 10 for all namespace?
c494237
to
5c511a8
Compare
5c511a8
to
eafe2cc
Compare
What changed?
Add dynamic config for per instance visibility API rate limit
Why?
Service protection.
How did you test it?
Existing tests?
Potential risks
rate limits are set wrong and frontend calls are accepted or rejected wrongfully
Is hotfix candidate?
Yes