Github user zhzhan commented on the issue:
https://github.com/apache/spark/pull/18694
The memory leak happens on following scenario. For example, in inner join,
the left side is exhausted, we will stop advance the right side. Because the
right side is not reach the end, the memory hold will not be released, cannot
be used by any other operator, for example, UnsafeShuffleWriter, causing more
spills.
Will locate the code logic in UnsafeExternalSorter that prevent the memory
being released.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
