Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11977719
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -322,6 +289,14 @@ class DAGScheduler(
missing.toList
}
+ private def startDAGSchedulerActors() {
+ dagSchedulerActorSupervisor = env.actorSystem.actorOf(Props(
+ new DAGSchedulerActorSupervisor(this)))
+ while (dagSchedulerActorSupervisor == null || eventProcessActor ==
null) {
--- End diff --
Okay, so in that case, we don't need to wait for it to be started, right?
We just need to wait for the reference to be non-null. So doing that in a
blocking way in the DAGScheduler constructor would be enough.
---
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.
---
