Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-41075065
It may be possible to prevent the display of the stack dumps in the
"DAGSchedulerActorSupervisor closes the SparkContext when EventProcessActor
crashes" test, but that's just cosmetic and can be done later.
We may also want to reorganize the DAGScheduler at some point to, e.g.,
move into the event actor some of the methods that are now `private[scheduler]`
in the `DAGScheduler` class. I know that @kayousterhout has some plans to
refactor much of the DAGScheduler, so the reorganization that I am suggesting
should probably wait until then.
Other than the few comments I just posted, this LGTM.
---
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.
---
