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

Long Term Testing: Memory Leaks #771

Closed
1 of 3 tasks
puckpuck opened this issue Mar 7, 2023 · 3 comments
Closed
1 of 3 tasks

Long Term Testing: Memory Leaks #771

puckpuck opened this issue Mar 7, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@puckpuck
Copy link
Contributor

puckpuck commented Mar 7, 2023

After running a 4-week test on a stable EKS cluster using m6i.large nodes I have found the following services to be experiencing memory leaks:

  • emailservice (severe)
  • loadgenerator (moderate)
  • redis (moderate)

This chart shows the 3 services' memory consumption and pod restarts over 3 weeks
Screenshot 2023-03-06 at 9 47 32 PM

This PR seems to be related to the emailservice though I'm unclear on it.
The redis leak is likey attributed to a lack of TTL when the cartservice is adding items to the cart
The loadgenerator may need further investigation to understand how and why the leak is being caused.

I have also found the frauddetectionservice to be experiencing a mild leak, though the service has not restarted after 4 weeks of running. I don't think we need to take any action on this at this point, but wanted to report it just in case.
Screenshot 2023-03-06 at 9 48 18 PM

@puckpuck puckpuck added bug Something isn't working v1.4 required for 1.4 release labels Mar 7, 2023
@cartersocha
Copy link
Contributor

Would basic garbage collection potentially help the loadgenerator?

@cartersocha
Copy link
Contributor

@ahayworth I took a look at the threads Pierre linked and you responded to some of the comments about the ruby / otel memory leak. Was there every any resolution or work around?

@austinlparker austinlparker removed the v1.4 required for 1.4 release label Apr 3, 2023
@austinlparker
Copy link
Member

Closing this as part of issue cleanup. If there's anything that needs to be done, please create a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants