Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38336957
I am far from an expert on this part of the code, but why not just
terminate in this case rather than continue with the DAG scheudler in a
potentially weird an inconsistent state.
An exception in the DAG scheduler is a serious failure which, in many
cases, indicates the job is doomed and cannot complete anyways.
As is, this seems like it could create some really hard-to-debug situations
where a user had a partial failure earlier on in their application then they
see some weird behavior later and can't figure out what's going on.
---
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.
---
