Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6750#discussion_r33707532
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -163,6 +163,12 @@ private[spark] class TaskSchedulerImpl(
this.synchronized {
val manager = createTaskSetManager(taskSet, maxTaskFailures)
activeTaskSets(taskSet.id) = manager
+ val taskSetsPerStage =
activeTaskSets.values.filterNot(_.isZombie).groupBy(_.stageId)
+ taskSetsPerStage.foreach { case (stage, taskSets) =>
+ if (taskSets.size > 1) {
+ throw new SparkIllegalStateException("more than one active
taskSet for stage " + stage)
+ }
+ }
--- End diff --
Perhaps the code could just look for an existing task set that matches the
stage ID of the task set being added? That should be a little better than the
filter / groupBy. Something like:
activeTaskSets.exists { case (_, ts) => ts.stageId == taskSet.stageId }
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
