Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15916
Yeah, I see. As I said in previous comment, the memory is released at the
end anyway.
I would guess the default setting as true is to find potential memory leak
during development. So turn it to false is a good idea?
This patch is coming from #15874 which hits the exception by @sethah.
Although `taskMemoryManager.cleanUpAllAllocatedMemory` can release memory
for us, I think it is just a safety network. Operators should release memory
themselves.
If you still think this is not necessary, I can close this.
---
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]
