Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/429#issuecomment-40662939
It seems to me that this is a safe change, since all `dagScheduler.start()`
does is create an actor that receives the messages in a separate thread, and
the only source of events posted is from `SparkContext` (user code) or
`TaskSchedulerImpl` (which happens only after task scheduler has started).
---
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.
---
