There is one more configuration option called spark.closure.serializer that can be used to specify serializer for closures.
Maybe in the the class you have Streaming Context as a field, so when spark tries to serialize the whole class it uses the spark.closure.serializer to serialize even the streaming context. Classes like StreamingContext may not work if serialized and deserialized in a different JVM(?). So I see two solutions one is to somehow avoid serializing StreamingContext, other is to override the default serialization method to serialize only the params required by streaming context and recreate it in the serialization step from the params -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Spark-1-0-1-NotSerialized-exception-a-bit-of-a-head-scratcher-tp11666p11703.html Sent from the Apache Spark User List mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
