Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/17744
We see the same issue on some of our clusters. I was planning on doing 2
things. Something like this to reduce that memory usage and then on the other
side you could change the shuffle fetcher to limit the # of blocks it fetches
in one try. The second is a separate jira though and could have the affect of
slowing down the shuffle and could also not be as effective if its a ton of
different reducers fetching but still a good option to have.
I think this approach is good for now. I ran a bunch of manual tests on the
cluster and memory has greatly improved.
+1. Thanks @jinxing64
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
