-
Notifications
You must be signed in to change notification settings - Fork 151
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
[#2300][Bug] Long tail tasks in the Write Stage retry phase results in data loss. #2301
base: master
Are you sure you want to change the base?
Conversation
0c3ccff
to
de38df3
Compare
de38df3
to
355f691
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2301 +/- ##
============================================
+ Coverage 52.27% 52.34% +0.07%
+ Complexity 3569 3362 -207
============================================
Files 543 513 -30
Lines 29797 27585 -2212
Branches 2779 2593 -186
============================================
- Hits 15575 14439 -1136
+ Misses 13227 12206 -1021
+ Partials 995 940 -55 ☔ View full report in Codecov by Sentry. |
@@ -118,6 +118,9 @@ public void reportShuffleWriteFailure( | |||
// Clear the metadata of the completed task, otherwise some of the stage's data will | |||
// be lost. | |||
shuffleManager.unregisterAllMapOutput(shuffleId); | |||
// Need to clear the mapStatus twice to prevent partition data loss due to the | |||
// long-tail task performed before the stage retry. | |||
shuffleManager.unregisterAllMapOutput(shuffleId); |
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.
Does it work? Just invoking twice in the same time point.
Sorry for the late reply, I'm busy for my work. |
What changes were proposed in this pull request?
The long-tail task in the previous Stage caused data loss, and this bug needs to be fixed.
Why are the changes needed?
Fix: #2300
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existential UT.