Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-136661103
@srowen Ok, I check the current code, it change to memory threshold per
task instead per thread. so that problem is still exist...
"
In the previous situation, it is aim to resolve memory_and_disk level
block, first unroll failed, but it will reserved unroll memory for this thread,
and that unroll memory part should release after that block already put into
disk, because nobody will use value for that unroll arrays. So it no necessary
to reserved that unroll memory part.
"
Do you agree that description or do I make that understandable?
---
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]
