Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11975529
--- 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 --
Also I agree this is a weird way to initialize stuff. Is there no way to
make DAGScheduler's constructor wait until the actor is up? AFAIK that will
also block the SparkContext thread so no submitJobs will be happening. There's
gotta be a way in Akka to send a message to an initializing ActorRef and wait
for it to reply, or otherwise achieve this.
---
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.
---
