Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-37711356
I know @pwendell has expressed concern about config option bloat so maybe
he has an opinion here...I would be in favor of not adding a config option
because it's a relatively small cost to serialize it (my sense is that even the
closures that are expensive to serialize take in the hundreds of milliseconds,
which compared to the time to run a job is typically very short) but I don't
feel strongly.
Re:keeping the check in the DAGScheduler, what are the cases when the
preemptive checking won't get done (other than in tests)?
---
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.
---
