[SPARK-52645] Enable ExitOnOutOfMemoryError JVM option by default
#266
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
dongjoon-hyun
force-pushed
the
SPARK-52645
branch
from
b89899d to
1188a1e
Compare
dongjoon-hyun
force-pushed
the
SPARK-52645
branch
from
1188a1e to
430dd54
Compare
Member
Author
|
cc @viirya , @peter-toth , @jiangzho |
viirya
approved these changes
Jul 2, 2025
Member
Author
|
Thank you, @viirya ! |
Member
Author
|
Oh, it seems that I found a bug. Let me fix that first. |
Member
Author
|
The bug fix PR is here. |
Member
Author
|
Merged to main. |
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?
This Pr aims to enable
ExitOnOutOfMemoryErrorJVM option by default.Why are the changes needed?
To help users identify the problematic situation as earlier as possible.
Does this PR introduce any user-facing change?
Yes, but OOM should not be ignored.
After this PR, the JVM will exit on the first
OutOfMemoryErrorit encounters, terminating the process with exit code 3.How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.