-
Notifications
You must be signed in to change notification settings - Fork 229
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
v0.9.1 - PR: #2031 - agent cpu usage explodes #2256
Labels
Comments
johnjcool
changed the title
v0.9.1 - PR: #2031 - Agent CPU usage explodes
v0.9.1 - PR: #2031 - agent cpu usage explodes
Mar 21, 2024
@johnjcool many thanks for reporting and debugging the issue. Could you verify if Fleet v0.9.2 fixes your issue? |
many thanks for quick response time :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
in contrast to 0.9.0 and 0.9.1 the fleet agent uses after the first DefaultResyncAgent much more cpu.
v0.9.1
v0.9.0
the main change between these two versions is this PR #2031. is it possible to revert this PR and fix the cpu usage problem first.__
Expected Behavior
small footprint at downstream clusters.
Steps To Reproduce
Environment
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: