Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1485#issuecomment-49444796
Slightly bigger point: both the 'fixed' and 'cached' executors from
`Executors` have some drawbacks:
- 'fixed' always keeps the given number of threads active even if they're
not doing anything
- 'cached' may create an unlimited number of threads
It's perfectly possible to create a `ThreadPoolExecutor` with core size 0
and a fixed maximum size. I wonder if that isn't the best choice here, and
actually, in other usages I see throughout Spark? Because a similar issue comes
up in about 10 places.
---
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.
---
