[SPARK-53636][CORE] Fix thread-safety issue in SortShuffleManager.unregisterShuffle #52386
+14
−11
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?
This PR fixes the thread-safetye issue in
SortShuffleManager.unregisterShuffle
by enforcing synchronous lock onmapTaskIds
's iteration. Besides, this PR also addresses the concern to enfore the type oftaskIdMapsForShuffle
asConcurrentHashMap
to ensure its thread-safety.Why are the changes needed?
Fix the potential thread-safety issue as pointed at #52337 (comment) and also the concern.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
No.