[SPARK-52124] Actively Releasing Disk Space After Application Completio… #50888
Conversation
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
…n in Spark Standalone Mode
Mrhs121
changed the title
|
@cloud-fan Hi~ could you help review this, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…n in Spark Standalone Mode
What changes were proposed in this pull request?
In the spark standalone mode, actively release the disk space occupied by the application in the work directory
Why are the changes needed?
When submitting applications using Spark in standalone mode, a folder is generated under the work directory on each node every time a application is submitted. The naming convention for these folders is, for example, app-20250212191730-0249. These folders contain the resource files that each node downloads from the master node when the application is submitted. Although there is a scheduled cleanup mechanism (spark.worker.cleanup.enabled), it is not immediate. If a large number of application are submitted in a short period of time, and each application depends on a significant amount of external resources, the disk space can be quickly exhausted.
Therefore, I suggest actively deleting the disk space occupied under the work directory after each application is completed.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No