GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/659
SPARK-1603: use auto-generated name in JobScheduler Actor
When Jenkins is pretty busy, the test of the "stop gracefully" case in
StreamingContextSuite sometimes failed with an unrelated change, the reason is
that "JobScheduler" (the actor name) is not unique, so it fails to start a new
actor.
The reason of this bug is that we assign a fixed name to the JobScheduler
Actor, and we assume that the actor should be stopped when StreamingContext is
stopped
(https://github.com/apache/spark/blob/master/streaming/src/main/scala/org/apache/spark/streaming/scheduler/JobScheduler.scala#L98),
actually, "nearly everything related to akka is asynchronous", we call the
stop() but get no guarantee on when the actor is really stopped
so there is a possibility to have two "JobScheduler" in akka's namespace
in this patch, I go with a pretty easy fix, use auto-generated name in the
actor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingCat/spark SPARK-1603
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/659.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #659
----
commit b21c887c93dc2c2c42696129f8170767a8ed7598
Author: CodingCat <[email protected]>
Date: 2014-05-06T02:35:41Z
use auto-generated name in JobScheduler Actor
----
---
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.
---
