-
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
plugin/storage/badger/spanstore: BenchmarkServiceIndexLimitFetch crashes #3301
Labels
Comments
Our badger implementation could really make use of some love. Are you interested in contributing a PR to get it better? Continuous benchmarking also sounds interesting :-) |
@jpkrohling sure I've mailed this ifx #3320 |
pavolloffay
pushed a commit
to pavolloffay/jaeger
that referenced
this issue
Oct 14, 2021
…ortable /mnt/* Previously the Benchmark code ALWAYS assumed that "/mnt/ssd/" would exist, yet when there is no permission or on read only systems, using it would fail. This change instead uses the benchmarks' temporary directory as the base for operations. Fixes jaegertracing#3301 Signed-off-by: Emmanuel T Odeke <emmanuel@orijtech.com>
yurishkuro
pushed a commit
that referenced
this issue
Oct 14, 2021
Previously the Benchmark code ALWAYS assumed that "/mnt/ssd/" would exist, yet when there is no permission or on read only systems, using it would fail. This change instead uses the benchmarks' temporary directory as the base for operations. Fixes #3301 Signed-off-by: Emmanuel T Odeke <emmanuel@orijtech.com> Co-authored-by: Emmanuel T Odeke <emmanuel@orijtech.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
I tried to continuously benchmark Jaeger using Orijtech Inc's continuous benchmarking product "Bencher" per https://dashboard.github.orijtech.com/?repo=orijtech/jaeger but it failed each time
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version (please complete the following information):
What troubleshooting steps did you try?
Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.
Additional context
Add any other context about the problem here.
I'd highly recommend adding continuous benchmarking to Jaeger so that things stay performant on every PR/commit without y'all even sweating at all, we handle all the heavy lifting for you. /cc-ing my colleagues @kirbyquerby @cuonglm.
The text was updated successfully, but these errors were encountered: