-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Using local copy of segment instead of downloading from remote #12863
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12863 +/- ##
============================================
+ Coverage 61.75% 62.04% +0.28%
+ Complexity 207 198 -9
============================================
Files 2436 2502 +66
Lines 133233 136414 +3181
Branches 20636 21106 +470
============================================
+ Hits 82274 84633 +2359
- Misses 44911 45503 +592
- Partials 6048 6278 +230
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ba01cec
to
5b8ec49
Compare
@klsince - Could you take a look? |
5b8ec49
to
ce49203
Compare
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.
good catch
apache#12863)" This reverts commit af8fd40.
Whats in the PR:
Local copy of segment is used to extract segment metadata.
Why its needed:
Segment is available locally (segment generation creates it) which can be used to extract metadata. Currently we are downloading segment from deep store which takes ~7-8 seconds per segment of size ~400Mb and there's unnecessary call to deep store. Removing this download, will speed minion execution by orders of seconds to minutes per minion.