-
Notifications
You must be signed in to change notification settings - Fork 1.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
[DOC]: The new quotas API does not allow to set check interval #10311
Comments
What does too much mean? Too small? Too big? |
Too big. |
I guess if you make it smaller you just overload the Admin API without gaining too much. BTW: The proposal specifically expects that |
I think it is useful to set a lower value, because a sudden and unexpected increase in the incoming bytes rate can fill up the disc in less than a minute, especially if you didn't leave room for this. The plugin project itself sets the check interval to 5 seconds as an example in the main readme. In general, I feel this is an important configuration to expose through the API.
Ok, I didn't remember that, but I don't think users read the proposal. Additionally, we have the following phrase in the changelog: the configuration of the plugin inside .spec.kafka.config is ignored and should be removed. |
I think you should plan with a sufficient buffer for this rather than play with the frequency of the check. |
I agree, but we have things like test clusters, perf and load tests, so there could be valid use cases for this. |
Discussed on the community call on 10.7.2024: We should update the documentation to suggest that additional options can be configured in |
Related problem
The default check interval is 60 seconds, which may be too much for some use cases.
The only way to configure this is to use
.spec.kafka.config
, which is undocumented.Suggested solution
Add
checkIntervalSec
to the quotas API with related documentation.Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: