[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008424#comment-14008424 ] Patrick Wendell commented on SPARK-1410: I ran into a similar issue SPARK-1923. It also fixed the issue to just upgrade to Scala 2.10.4. Thanks [~mengxr] for posting this - I was two hours into debugging Spark when I found this post :P Since this seems to be a Scala/SBT issue I'm going to mark it as resolved, but we can re-open it if users are still having issues post upgrade. > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003242#comment-14003242 ] Conrad Dean commented on SPARK-1410: Had the same issue. Was trying to run a stand alone scala app from https://spark.apache.org/docs/0.9.0/quick-start.html with Joda and some other dependencies. sbt 0.13.2 was giving me this error, downgraded to 0.12.4 and everything worked. Later upgraded sbt back to 0.13.2 and upgraded scala from 2.10.3 to 2.10.4 and everything works. > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000859#comment-14000859 ] Gerard Maas commented on SPARK-1410: Had exact the same issue with sbt 0.13.0 and Scala 2.10.3. Setting scala version to 2.10.4 worked for me. > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959501#comment-13959501 ] Michael Armbrust commented on SPARK-1410: - So I haven't tracked down why this is the case, but I think changing build.sbt to: scalaVersion := "2.10.4" instead might fix this problem. > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959363#comment-13959363 ] Xiangrui Meng commented on SPARK-1410: -- The code is available at https://github.com/mengxr/mllib-grid-search If sbt.version is changed to 0.13.0 or 0.13.1, `sbt/sbt "run ..."` throws the following exception: ~~~ [error] (run-main-0) org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: sbt.classpath.ClasspathFilter@45307fb org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: sbt.classpath.ClasspathFilter@45307fb at org.apache.spark.scheduler.DAGScheduler$$anonfun$org$apache$spark$scheduler$DAGScheduler$$abortStage$1.apply(DAGScheduler.scala:1010) at org.apache.spark.scheduler.DAGScheduler$$anonfun$org$apache$spark$scheduler$DAGScheduler$$abortStage$1.apply(DAGScheduler.scala:1008) 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.org$apache$spark$scheduler$DAGScheduler$$abortStage(DAGScheduler.scala:1008) at org.apache.spark.scheduler.DAGScheduler$$anonfun$processEvent$10.apply(DAGScheduler.scala:595) at org.apache.spark.scheduler.DAGScheduler$$anonfun$processEvent$10.apply(DAGScheduler.scala:595) at scala.Option.foreach(Option.scala:236) at org.apache.spark.scheduler.DAGScheduler.processEvent(DAGScheduler.scala:595) at org.apache.spark.scheduler.DAGScheduler$$anonfun$start$1$$anon$2$$anonfun$receive$1.applyOrElse(DAGScheduler.scala:146) 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) ~~~ > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SPARK-1410) Class not found exception with application launched from sbt 0.13.x
[ https://issues.apache.org/jira/browse/SPARK-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959265#comment-13959265 ] Michael Armbrust commented on SPARK-1410: - I don't understand how the classloader is ending up being required on the worker side. Can you share a command to reproduce this? > Class not found exception with application launched from sbt 0.13.x > --- > > Key: SPARK-1410 > URL: https://issues.apache.org/jira/browse/SPARK-1410 > Project: Spark > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Xiangrui Meng > > sbt 0.13.x use its own loader but this is not available at worker side: > org.apache.spark.SparkException: Job aborted: ClassNotFound with classloader: > sbt.classpath.ClasspathFilter@47ed40d > A workaround is to switch to sbt 0.12.4. -- This message was sent by Atlassian JIRA (v6.2#6252)
