[SPARK-33710][ Shuffle] [YARN] Shuffle index use guava cache OOM, Yarn NodeManager GC alarm #30672
+1
−1
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?
Guava cache capacity limit join key size statistics
Why are the changes needed?
When using guava cache, the key size is not counted, resulting in memory overflow. If the value is infinitely small, then the heap memory can store countless File type keys. I think this is a defect
Does this PR introduce any user-facing change?
No
How was this patch tested?
No
Use the Memory Analyzer Tool to locate the shuffle index module

There are a lot of file path information of shuffle index in memory, The path is from shuffleIndexCache of ExternalShuffleBlockResolver
/** * Caches index file information so that we can avoid open/close the index files * for each block fetch. */ private final LoadingCache<File, ShuffleIndexInformation> shuffleIndexCache;
ISSUE SPARK-33710
YARN GC ALARM