Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11458208
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1128,13 +1108,155 @@ class DAGScheduler(
}
def stop() {
+ logInfo("Stopping DAGScheduler")
if (eventProcessActor != null) {
eventProcessActor ! StopDAGScheduler
}
+ if (dagSchedulerActorSupervisor != null) {
+ dagSchedulerActorSupervisor ! StopDAGScheduler
+ }
--- End diff --
Yeah, it looks like we don't need the scheduler.stop() there because
LocalSparkContext#afterEach will already do that. I still haven't figured out
why I am seeing the eventProcessActor's postStop called twice as often as I
expected. That probably doesn't hurt anything, but I still want to figure out
just what is 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.
---
