Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/10024#issuecomment-212793811
@davies I also have run unit tests with big number N.
How about add a config "spark.shuffle.spill.reservedMemory"? its default is
true. It does not force to spilling when its value is true. Maybe 2.1 version
the config can be deleted.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
