[CELEBORN-1544][0.4] ShuffleWriter needs to call close finally to avoid memory leaks #2718
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.
Backport CELEBORN-1544 (#2661 and #2663) to branch-0.4
What changes were proposed in this pull request?
This PR aims to fix a possible memory leak in ShuffleWriter.
Why are the changes needed?
When we turn on
spark.speculation=true
or we kill the executing SQL, the task may be interrupted. At this time,ShuffleWriter
may not call close.At this time,
DataPusher#idleQueue
will occupy some memory capacity (celeborn.client.push.buffer.max.size
*celeborn.client.push.queue.capacity
) and the instance will not be released.Does this PR introduce any user-facing change?
No
How was this patch tested?
Production testing
Current
PR