What version of Mesos are you using? We tagged a release-candidate of Mesos that had a bug when used with frameworks that were using older JARs (like Spark). The manifestation of the bug was some protocol buffers didn't parse, such as SlaveInfo, resulting in a NullPointerException.
Until Spark gets a new JAR (and assuming you're not using the buggy release candidate of Mesos) then you can fix this problem by restarting your slave after removing it's meta-directory. Please share the version (in fact, versions of Mesos that you've upgraded over time would be great). And let us know how it goes! Ben. On Mon, Jan 13, 2014 at 10:19 AM, deric <[email protected]> wrote: > I've updated to the newest trunk version, and still all tasks are getting > lost: > > java.lang.NullPointerException > at > > com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:509) > at > > com.typesafe.config.impl.Parseable$ParseableResources.rawParseValue(Parseable.java:492) > at > com.typesafe.config.impl.Parseable.parseValue(Parseable.java:171) > at > com.typesafe.config.impl.Parseable.parseValue(Parseable.java:165) > at com.typesafe.config.impl.Parseable.parse(Parseable.java:204) > at > com.typesafe.config.ConfigFactory.parseResources(ConfigFactory.java:760) > at > com.typesafe.config.ConfigFactory.parseResources(ConfigFactory.java:769) > at org.apache.spark.SparkConf.<init>(SparkConf.scala:37) > at org.apache.spark.executor.Executor.<init>(Executor.scala:60) > at > > org.apache.spark.executor.MesosExecutorBackend.registered(MesosExecutorBackend.scala:58) > Exception in thread "Thread-0" > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/Running-Spark-on-Mesos-tp503p505.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. >
