Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18694
I'd doubt this is actually a memory leak as `UnsafeExternalSorter` already
avoids memory leaks by registering a cleanup task:
https://github.com/apache/spark/blob/master/core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java#L159
Btw, as the comment indicates, you still can't avoid hold the memory for
the cases like the operator followed by limit.
---
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]
