-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Update Elasticsearch to use olivere/elastic/v7 #7244
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
Update Elasticsearch to use olivere/elastic/v7 #7244
Conversation
|
We already ignore the leaking parts of the code from ES in internal/testutils/leakcheck.go Is there another candidate we need to add? |
|
Hmm, why the CI keeps failing ? |
Please stamp #7247 so that the logs are better for troubleshooting. |
|
rerunning with better logging |
|
The error is still there I don't recall what's the deal with these mismatching counts, can you look into what the test is doing? In retrospect I think it would've been better to separate large trace test with a test that contains spans with duplicate span IDs (the latter could be on a much smaller trace). |
|
Hi, it's actually that the tests is trying to verify two behaviors at once:
|
Yes, and we should split that (want to create a PR?) But what I don't understand is the different numbers. The test is generating 10008 spans (intentionally more than the default 10k limit in some DBs), but it's also creating dups every 100 spans (for a total of 100). So if dups are removed I would expect the total to be 9908, not round 9900. Unfortunately, we don't seem to log these numbers in the successful runs, to compare with your diff. |
Actually, I think this is precisely the issue and could be related to your changes - despite duplicate span IDs we still expect to load all spans from storage, and only later to dedupe then. But this new log line says we were only able to load exactly 10k spans, which is the ES default doc limit which we were somehow working around (possible via this total hits count). |
|
Yeah, I think it's the problem |
Sure I can make pull request to solve this tomorrow |
Do you think we should modify the test to write 10k spans instead of 10k + 8 ? |
|
absolutely not, it's intentionally writing >10k. If it was only writing 10k then your change would've passed and we wouldn't catch the bug. |
8c66d34 to
0321b3d
Compare
Signed-off-by: pipiland2612 <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: pipiland2612 <[email protected]>
Signed-off-by: pipiland2612 <[email protected]>
0321b3d to
7a7ac74
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7244 +/- ##
==========================================
+ Coverage 96.18% 96.20% +0.02%
==========================================
Files 369 369
Lines 22184 22181 -3
==========================================
+ Hits 21338 21340 +2
+ Misses 632 628 -4
+ Partials 214 213 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
||
| s := s.sourceFn(query, nextTime) | ||
| s := s.sourceFn(query, nextTime). | ||
| TrackTotalHits(true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// TotalHits is a convenience function to return the number of hits for
// a search result. The return value might not be accurate, unless
// track_total_hits parameter has set to true.
The totalhits function has this comment. So I enable it
Signed-off-by: pipiland <[email protected]>
|
hi @yurishkuro, the pr is ready for your review |
Signed-off-by: pipiland2612 <[email protected]>
7f7122c to
d6ec319
Compare
#7248) ## Which problem is this PR solving? - Comment [split GetLargeSpan](#7244 (comment)) ## Description of the changes - Split GetLargeSpan test into 2 tests: GetLargeSpans and GetSpanWithDuplicate ## How was this change tested? - make lint test ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: pipiland2612 <[email protected]> Signed-off-by: Yuri Shkuro <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]> Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
|
Thanks for your support! |
5b2b1d2
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger:make lint testjaeger-ui:npm run lintandnpm run test