Github user tsdeng commented on the pull request:
https://github.com/apache/spark/pull/3302#issuecomment-63362905
Yeah, I guess we need that lower bound when memory threshold is not
"pushable", meaning when memory is too small and you can not acquire memory...
I agree this behavior is kinda weird. Maybe it's used as "the last defense"?
Please refer to https://issues.apache.org/jira/browse/SPARK-4452 why this last
defense saved my svd job. I'm also working on another branch documented on
SPARK-4452 to make a deeper fix for memory allocation for spillable objects
---
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]
