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

Pods of user-simulator get OOMKilled #28

Closed
W3D3 opened this issue Jan 31, 2023 · 0 comments · Fixed by #29
Closed

Pods of user-simulator get OOMKilled #28

W3D3 opened this issue Jan 31, 2023 · 0 comments · Fixed by #29
Assignees
Labels
bug Something isn't working

Comments

@W3D3
Copy link
Contributor

W3D3 commented Jan 31, 2023

Environment

  • Client OS (e.g., Linux, macOS, Windows): Kubuntu 22.10
  • Unguard Version [e.g. 1.0.0]: 0.7.0
  • Kubernetes version (kubectl version): 1.25

Describe the bug
Pods of the user-simulator deployment will periodically run out of memory before they terminate on their own and then be killed by Kubernetes (OOMKilled event). In some instances K8s will then back off from restarting them, making them not generate any load until they are manually restarted again.

To Reproduce
Deploy unguard and let the user-simulator run for some time.

Suggestion
Making the user-simulator a Kubernetes cronjob would make it more resilient against crashes, as there may be a memory leak in a library used by the user simulator.

@W3D3 W3D3 added the bug Something isn't working label Jan 31, 2023
@W3D3 W3D3 self-assigned this Jan 31, 2023
@W3D3 W3D3 closed this as completed in #29 Feb 8, 2023
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

Successfully merging a pull request may close this issue.

1 participant