feat(spark): introduce options to control the memory requested#2747
Open
zuston wants to merge 3 commits intoapache:masterfrom
Open
feat(spark): introduce options to control the memory requested#2747zuston wants to merge 3 commits intoapache:masterfrom
zuston wants to merge 3 commits intoapache:masterfrom
Conversation
zuston
changed the title
Contributor
|
Could we add some tests for this feature? |
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
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?
introduce options to control the max memory requested
Why are the changes needed?
Found that some large spark jobs failed due to the OOM. but the shuffle writer acquired too much memory but haven't been spilled due to the high pressure of shuffle-servers. For this case, I hope we could introduce the options to control the uniffle client memory usage.
Does this PR introduce any user-facing change?
Yes.
How was this patch tested?
Unit tests