-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Collector with badger storage failed to start after crash #1832
Labels
storage/badger
Issues related to badger storage
Comments
cc @burmanm |
burmanm
added a commit
to burmanm/jaeger
that referenced
this issue
Oct 7, 2019
burmanm
added a commit
to burmanm/jaeger
that referenced
this issue
Oct 7, 2019
…aegertracing#1832 Signed-off-by: Michael Burman <[email protected]>
radekg
pushed a commit
to Klarrio/jaeger
that referenced
this issue
Oct 28, 2019
…aegertracing#1832 (jaegertracing#1842) Signed-off-by: Michael Burman <[email protected]> Signed-off-by: radekg <[email protected]>
backjo
pushed a commit
to backjo/jaeger
that referenced
this issue
Dec 19, 2019
…aegertracing#1832 (jaegertracing#1842) Signed-off-by: Michael Burman <[email protected]> Signed-off-by: Jonah Back <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirement
Stable recovering of jaeger docker container
all-in-one
withbadger
storage backend after crash or OOM kill.Problem
Jaeger docker container (
all-in-one
) failed to start. Following error occurs:Proposal
Provide option for enabling truncate in badger. See: dgraph-io/badger#744
The text was updated successfully, but these errors were encountered: