optimize driver memory #8
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 type of PR is this?
enhancements：reduce driver memory usage
What this PR does / why we need it:
When running large data task，spark driver offen encounters oom error. By analyzing the heap dump，I found there are 185,657,950 PartitionInfo instances that occupy 4GB memory. Most PartitionInfo instances are referenced by ShuffleTaskManager.shuffleEpochSetMap attribute. This attribute type is ConcurrentHashMap[String, ConcurrentHashMap[Int, util.List[PartitionInfo]]]. It's only used to check shuffle data loss.
We can change List to Set, remove duplicate PartitionInfo. After doing this, the memory is used much less than before.