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

Memory Configurations for Loki #191

Closed
ahus1 opened this issue Dec 25, 2018 · 8 comments
Closed

Memory Configurations for Loki #191

ahus1 opened this issue Dec 25, 2018 · 8 comments

Comments

@ahus1
Copy link

ahus1 commented Dec 25, 2018

I'm looking for documentation how to configure and/or calculate the memory (RAM) used by loki.

@danieldabate
Copy link
Contributor

Any information related to this topic would be very useful for us too. We are running Loki and some queries get it OOMKilled. I can just keep giving it more and more RAM, but would like to have more information to take a better decision.

@agolomoodysaada
Copy link

agolomoodysaada commented May 10, 2019

Experiencing this pain as well. A query shouldn't cause Loki to crash. At worst, we should just take longer to return results instead of eating as much RAM as possible.

@cyriltovena
Copy link
Contributor

Are you still experiencing the same?

@agolomoodysaada
Copy link

I'm experiencing this with grafana/loki@sha256:00c8c4047b282b639861c2a1fe4ffda42b0961420b69ad58e620380340037ef

@agolomoodysaada
Copy link

I updated to the latest version and still experiencing OOMKilled events

@agolomoodysaada
Copy link

actually... I'm now seeing level=warn ts=2019-05-17T14:32:54.082466654Z caller=logging.go:49 traceID=55bd9a8915b11fb6 msg="GET /ready (500) 71.86µs Response: \"Not ready: waiting for 1m0s after startup\\n\" ws: false; Accept-Encoding: gzip; Connection: close; User-Agent: kube-probe/1.11+; "

@agolomoodysaada
Copy link

But still OOMKilled happening even after adding memory to 8G

@cyriltovena
Copy link
Contributor

You should not need more than 10gib now even if you're using Loki intensively.

periklis added a commit to periklis/loki that referenced this issue Oct 12, 2023
Update from upstream repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants