You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/05/15 15:50:00 UTC

[jira] [Resolved] (SPARK-864) DAGScheduler Exception if A Node is Added then Deleted

     [ https://issues.apache.org/jira/browse/SPARK-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-864.
-----------------------------
    Resolution: Cannot Reproduce

Closing as it looks exceptionally stale at this point and haven't seen similar reports

> DAGScheduler Exception if A Node is Added then Deleted
> ------------------------------------------------------
>
>                 Key: SPARK-864
>                 URL: https://issues.apache.org/jira/browse/SPARK-864
>             Project: Spark
>          Issue Type: Bug
>          Components: Scheduler
>    Affects Versions: 0.8.0
>            Reporter: Patrick Cogan
>            Assignee: xiajunluan
>
> According to [~markhamstra], if you run the UI tester locally and remove a slave, then add another slave, everything freezes. UPDATE: This appears to be caused by the DAGScheduler:
> {code}
> Exception in thread "DAGScheduler" java.util.NoSuchElementException: key not found: 2
> 	at scala.collection.MapLike$class.default(MapLike.scala:225)
> 	at scala.collection.mutable.HashMap.default(HashMap.scala:45)
> 	at scala.collection.MapLike$class.apply(MapLike.scala:135)
> 	at scala.collection.mutable.HashMap.apply(HashMap.scala:45)
> 	at spark.scheduler.DAGScheduler.spark$scheduler$DAGScheduler$$submitMissingTasks(DAGScheduler.scala:515)
> 	at spark.scheduler.DAGScheduler.spark$scheduler$DAGScheduler$$submitStage(DAGScheduler.scala:481)
> 	at spark.scheduler.DAGScheduler$$anonfun$resubmitFailedStages$3.apply(DAGScheduler.scala:383)
> 	at spark.scheduler.DAGScheduler$$anonfun$resubmitFailedStages$3.apply(DAGScheduler.scala:382)
> 	at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:34)
> 	at scala.collection.mutable.ArrayOps.foreach(ArrayOps.scala:38)
> 	at spark.scheduler.DAGScheduler.resubmitFailedStages(DAGScheduler.scala:382)
> 	at spark.scheduler.DAGScheduler.spark$scheduler$DAGScheduler$$run(DAGScheduler.scala:433)
> 	at spark.scheduler.DAGScheduler$$anon$1.run(DAGScheduler.scala:135)
> {code}
> This code is related to the FairScheduler change. Hey [~andrew xia] - could you take a look at this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org