[#1309] fix(spark): WriteBufferManager in Spark2 does not use a reassigned shuffle server. - #1310
Merged
Merged
Conversation
…oes not use a reassigned shuffle server.
Contributor
Author
|
@jerqi @leixm Found a BUG, review it for me sometime. |
roryqi
approved these changes
Nov 11, 2023
roryqi
changed the title
xianjingfeng
pushed a commit
that referenced
this pull request
Nov 17, 2023
…igned shuffle server. (#1310) ### What changes were proposed in this pull request? In Spark2, after a write failure, ShuffleBlockInfo is not built using the new shuffle server after the shuffle server is reassigned. ### Why are the changes needed? Fix: #1309 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Existing UT. (cherry picked from commit d5de299)
xianjingfeng
added a commit
that referenced
this pull request
Nov 20, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
In Spark2, after a write failure, ShuffleBlockInfo is not built using the new shuffle server after the shuffle server is reassigned.
Why are the changes needed?
Fix: #1309
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing UT.