Github user zhzhan commented on the issue:
https://github.com/apache/spark/pull/18694
Currently the patch helps the scenario such as Join(A, Join(B,C)). It is
critical for us because we have some internal development in which each stage
may consists of tens of sort operators. We found each operators takes the
memory without releasing the current page, and causes a lot of spills. Such
memory leak becomes critical (ShuffledHashJoin has similar issues and we did
not hit issues caused by Limit).
To me, the leak itself is a bug. If it is agreed that we should fix this
type of leak, we can find a more elegant way, such as new close() interface, to
avoid the overhead.
---
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
