You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kay Ousterhout (JIRA)" <ji...@apache.org> on 2014/07/24 01:14:38 UTC
[jira] [Updated] (SPARK-1726) Tasks that fail to serialize remain
in active stages forever.
[ https://issues.apache.org/jira/browse/SPARK-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kay Ousterhout updated SPARK-1726:
----------------------------------
Affects Version/s: 1.0.1
Fix Version/s: (was: 1.1.0)
[~marmbrus] Sorry I spoke too soon -- this is still broken but much less broken than before. By default, SparkContext.clean() now checks if tasks are serializable, which typically prevents this problem because the stage never gets submitted. However, checking if tasks are serializable can be disabled (see https://github.com/apache/spark/pull/143), in which case you can still see this problem.
> Tasks that fail to serialize remain in active stages forever.
> -------------------------------------------------------------
>
> Key: SPARK-1726
> URL: https://issues.apache.org/jira/browse/SPARK-1726
> Project: Spark
> Issue Type: Bug
> Components: Web UI
> Affects Versions: 1.0.1
> Reporter: Michael Armbrust
> Assignee: Andrew Or
> Attachments: ZombieTask.tiff
>
>
> In the spark shell.
> {code}
> scala> class Adder(x: Int) { def apply(a: Int) = a + x }
> defined class Adder
> scala> val add = new Adder(10)
> scala> sc.parallelize(1 to 10).map(add(_)).collect()
> {code}
> You get:
> {code}
> org.apache.spark.SparkException: Job aborted due to stage failure: Task not serializable: java.io.NotSerializableException: $iwC$$iwC$$iwC$$iwC$Adder
> at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1033)
> at org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1017)
> at org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1015)
> at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
> at org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1015)
> at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$submitMissingTasks(DAGScheduler.scala:770)
> at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$submitStage(DAGScheduler.scala:713)
> at org.apache.spark.scheduler.DAGScheduler.handleJobSubmitted(DAGScheduler.scala:697)
> at org.apache.spark.scheduler.DAGSchedulerEventProcessActor$$anonfun$receive$2.applyOrElse(DAGScheduler.scala:1176)
> at akka.actor.ActorCell.receiveMessage(ActorCell.scala:498)
> at akka.actor.ActorCell.invoke(ActorCell.scala:456)
> at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:237)
> at akka.dispatch.Mailbox.run(Mailbox.scala:219)
> at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:386)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> {code}
> However, the web ui is messed up. See attached screen shot.
--
This message was sent by Atlassian JIRA
(v6.2#6252)