Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@spark.apache.org
Date: Thu, 24 Jul 2014 05:44:38 +0000 (UTC)
From: "Kay Ousterhout (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12712435.1399327841406.35379.1406180678898@arcas>
In-Reply-To: <JIRA.12712435.1399327841406@arcas>
References: <JIRA.12712435.1399327841406@arcas>
Subject: [jira] [Assigned] (SPARK-1726) Tasks that fail to serialize remain
 in active stages forever.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kay Ousterhout reassigned SPARK-1726:
-------------------------------------

    Assignee: Kay Ousterhout  (was: Andrew Or)

> 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: Kay Ousterhout
>         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)