[SPARK-50421]fix executor related memory config incorrect when multiple resource profile worked #48963
+26
−0
Conversation
This file contains 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
|
@tgravescs Would you help to review this commit? |
zjuwangg
force-pushed
the
m_fixConfig
branch
from
d28c67f
to
1e41213
Compare
zjuwangg
changed the title
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.
What changes were proposed in this pull request?
Reset the executor's env memory related config when resource profile is not as the default resource profile!
Why are the changes needed?
When multiple resource profile exists in the same spark application, now the executor's memory related config is not override by resource profile's memory size, which will cause maxOffHeap in
UnifiedMemoryManageris not correct.See https://issues.apache.org/jira/browse/SPARK-50421 for more details
Does this PR introduce any user-facing change?
No
How was this patch tested?
To be added
Was this patch authored or co-authored using generative AI tooling?
No