Skip to content
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

Dynamically configure historical cache limit in logging app #6299

Closed
maxtropets opened this issue Jun 27, 2024 · 1 comment · Fixed by #6346
Closed

Dynamically configure historical cache limit in logging app #6299

maxtropets opened this issue Jun 27, 2024 · 1 comment · Fixed by #6346
Assignees

Comments

@maxtropets
Copy link
Collaborator

maxtropets commented Jun 27, 2024

#6282 introduced fixed logging app cache limit to test it out in historical perf test.

It's better to make it callable from the client. A nice thing to have would be to somehow verify cache shrinking in e2e tests.

#6282 (comment)

@achamayou
Copy link
Member

For now, since this is a global setting, let's make this a node configuration setting that the operator can set at startup. We can revisit it if there is a need for something more specific (but might need to have separate cache quotas for the C++ and programmable endpoints for example).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants