Also please make sure you are specifying the fully qualified name of
registrator class in the sparkconf configuration correctly.
On Dec 11, 2014 5:57 PM, "bonnahu" wrote:
> class MyRegistrator implements KryoRegistrator {
>
> public void registerClasses(Kryo kryo) {
> kryo
class MyRegistrator implements KryoRegistrator {
public void registerClasses(Kryo kryo) {
kryo.register(ImpressionFactsValue.class);
}
}
change this class to public and give a try
--
View this message in context:
http://apache-spark-user-list.1001560.n
Hi,
i just migrate to 1.0. Still having the same issue.
Either with or without the custom registrator. Just the usage of the
KryoSerializer triggers the exception immediately.
I set the kryo settings through the property:
System.setProperty("spark.serializer", "org.apache.spark.serializer.
KryoS
I am experiencing the same issue (I tried both using Kryo as serializer and
increasing the buffer size up to 256M, my objects are much smaller though).
I share my registrator class just in case:
https://gist.github.com/JordiAranda/5cc16cf102290c413c82
Any hints would be highly appreciated.
Thank
Hi Andrea,
What version of Spark are you using? There were some improvements in how
Spark uses Kryo in 0.9.1 and to-be 1.0 that I would expect to improve this.
Also, can you share your registrator's code?
Another possibility is that Kryo can have some difficulty serializing very
large objects.
UP, doesn't anyone know something about it? ^^
2014-05-06 12:05 GMT+02:00 Andrea Esposito :
> Hi there,
>
> sorry if i'm posting a lot lately.
>
> i'm trying to add the KryoSerializer but i receive this exception:
> 2014 - 05 - 06 11: 45: 23 WARN TaskSetManager: 62 - Loss was due to
> java.io.EO
