I should clarify: I'm not using GraphX, it's a different application-specific Kryo registrator that causes the same stacktrace ending in PARSING_ERROR:
com.esotericsoftware.kryo.KryoException: java.io.IOException: failed to uncompress the chunk: PARSING_ERROR(2) com.esotericsoftware.kryo.io.Input.fill(Input.java:142) com.esotericsoftware.kryo.io.Input.require(Input.java:169) com.esotericsoftware.kryo.io.Input.readInt(Input.java:325) com.esotericsoftware.kryo.io.Input.readFloat(Input.java:624) com.esotericsoftware.kryo.serializers.DefaultSerializers$FloatSerializer.read(DefaultSerializers.java:127) com.esotericsoftware.kryo.serializers.DefaultSerializers$FloatSerializer.read(DefaultSerializers.java:117) com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:732) com.esotericsoftware.kryo.serializers.CollectionSerializer.read(CollectionSerializer.java:109) com.esotericsoftware.kryo.serializers.CollectionSerializer.read(CollectionSerializer.java:18) com.esotericsoftware.kryo.Kryo.readClassAndObject(Kryo.java:732) ... my registrator Ankur from my read of the ticket there's not a root cause identified for those PARSING_ERROR exceptions in GraphX yet? Andrew On Mon, Sep 15, 2014 at 2:10 PM, Ankur Dave <ankurd...@gmail.com> wrote: > At 2014-09-15 08:59:48 -0700, Andrew Ash <and...@andrewash.com> wrote: > > I'm seeing the same exception now on the Spark 1.1.0 release. Did you > ever > > get this figured out? > > > > [...] > > > > On Thu, Aug 21, 2014 at 2:14 PM, npanj <nitinp...@gmail.com> wrote: > >> I am getting PARSING_ERROR while running my job on the code checked out > up > >> to commit# db56f2df1b8027171da1b8d2571d1f2ef1e103b6. > > The error is because I merged a GraphX PR that introduced a > nondeterministic bug [1]. I reverted the faulty PR, but it was too late for > the 1.1.0 release. The problem should go away if you use branch-1.1 or > master. Sorry about that... > > Ankur > > [1] https://issues.apache.org/jira/browse/SPARK-3400 >
