-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Elastic Agent] Fix lazy acker to only add new actions to the batch #27981
Conversation
Pinging @elastic/agent (Team:Agent) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
This pull request is now in conflicts. Could you fix it? 🙏
|
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.
change lgtm
/package |
…lastic#27981) * Fix lazy acker. * Add changelog.
…lastic#27981) (elastic#28061) * Fix lazy acker. * Add changelog. (cherry picked from commit 1fcb57e) Co-authored-by: Blake Rouse <blake.rouse@elastic.co>
What does this PR do?
This modifies the
lazy.Acker
to only add a new action to the batch (aka. queue). This ensures that if the same action is added to the batch it is not duplicated.Why is it important?
Because of the way the Fleet mode of the Elastic Agent is designed it will keep adding the same actions over and over again to the lazy.Acker because the underlying Acker fails to ack the action.
This causes the queue to grow indefinitely that causes the process to consume all the memory of the system.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues