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

Loki curator container memory usage starts to gradual increase until is OOMKiled. #119

Closed
vlvasilev opened this issue Apr 5, 2022 · 0 comments · Fixed by #120
Closed
Labels
area/logging Logging related kind/bug Bug priority/1 Priority (lower number equals higher priority)
Milestone

Comments

@vlvasilev
Copy link
Collaborator

What happened:
After continuous work, the Loki curator container memory usage starts to gradual increase.
There is no trace of garbage collection triggering until reaching the memory limit but after time the container is OOMKilled.

What you expected to happen:
I am expecting the Loki curator container memory usage to be nearly constant with spikes only when the deletion of files is triggered.

How to reproduce it (as minimally and precisely as possible):
Currently, this issue is present in all landscapes mainly for the central Loki pod.

Anything else we need to know:

Environment:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logging Logging related kind/bug Bug priority/1 Priority (lower number equals higher priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants