-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Jaeger is OOMKilled when use badger as storage #2987
Comments
I think this isn't related to the operator, but more general to Jaeger and its usage of Badger. |
We have a few changes in the queue for badger as storage for Jaeger, but it might take a while for us to work on it. If this is critical to you, I can point you to the places in the code for you to take a look at. |
we really want to have persistent data for the tracing. |
You can use Cassandra or Elasticsearch for that, which are actually recommended if you need to scale your deployment... In any case, here's the badger code: https://github.com/jaegertracing/jaeger/tree/master/plugin/storage/badger |
This should have been fixed by #3096. If you are still experiencing this, feel free to reopen. |
I still have this behavior with all in one image v1.49, weird thing is the OOM happens at startup with no load at all (probably when badger is getting reopened). Edit: it seems /keys are not evicted whereas /data is almost empty:
Mystery solved: spring-boot with hikari+sleuth will trigger spans even for |
version: all-in-one:1.18.1
issue:
when i use badge as storage, Jaeger requests much more memory than in-memory storage and it keeps OOMKiller.
At the beginning Jaeger requests just hundred MB memory when it uses in-memory storage. But it requests over 5Gi memory when changed to Badge.
Jaeger yaml:
The text was updated successfully, but these errors were encountered: