Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11975810
--- 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 --
Alright, that should be better than a busy loop. I'm surprised that
messages to an ActorRef aren't queued while it's initializing. It's also quite
possible that your initialization isn't happening the way you believe and the
DAGScheduler constructor is called *after* or concurrently with submitJob.
---
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.
---
