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

[Auditbeat] Memory leak in 7.5.2 #16877

Closed
andrewstucki opened this issue Mar 6, 2020 · 1 comment · Fixed by #17500
Closed

[Auditbeat] Memory leak in 7.5.2 #16877

andrewstucki opened this issue Mar 6, 2020 · 1 comment · Fixed by #17500
Assignees

Comments

@andrewstucki
Copy link

  • Version: 7.5.2
  • Operating System: Linux
  • Discuss Forum URL: https://discuss.elastic.co/t/auditbeat-memory-leak-in-7-5-2/218335
  • Steps to Reproduce:
    1. Monitor network flows using the system/socket module/dataset
    2. Start a long-lived process which opens up a lot of sockets
    3. Generate enough noise in the kernel where inet_release (or do_exit) or any of the return probes roll off the ring buffer prior to us consuming them
    4. Watch memory increase unbounded over time

Description:

We don't have cache expiration policies for sockets, cached processes, or the short-term cache we use for tracking kprobe call/return pairs. As a result, any missed calls that would normally result in a cache eviction will result in a memory leak (writing to a map and never deleting the key/value).

We should add a cache expiration policy to get rid of potential memory leaks

@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

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