Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38164160
hey, @markhamstra, that's my bad, I just added the logging lines
BTW, I also thought to restart the running stage which causes the restart
of the dagScheduler, I think it's doable, though I didn't implement it...we can
set a maximum limit on the restart of dagScheduler. But since the restart is
triggered by the crash of dagScheduler, which is more serious than the user
code bug, which option is the best one?
---
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.
---
