Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/23083
Looking at the code, we are trying to fix 2 memory leaks: the task
completion listener in `ShuffleBlockFetcherIterator`, and the
`CompletionIterator`. If that's case, can you say that in the PR description?
For the task completion listener, I think it's an overkill to introduce a
new API, do we know exactly where we leak the memory? and can we null it out
when the `ShuffleBlockFetcherIterator` reaches to its end?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
