I am seeing the same error as well since upgrading to Spark1.1:
14/09/26 15:35:05 ERROR executor.Executor: Exception in task 1032.0 in
stage 5.1 (TID 22449)
com.esotericsoftware.kryo.KryoException: java.io.IOException: failed to
uncompress the chunk: PARSING_ERROR(2)
at com.esotericsoftwar
Hi Andrew,
No I could not figure out the root cause. This seems to be non-deterministic
error... I didn't see same error after rerunning same program. But I noticed
same error on a different program.
First I thought that this may be related to SPARK-2878, but @Graham replied
that this looks irre
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.
At 2014-09-15 08:59:48 -0700, Andrew Ash 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 wrote:
>> I am getting PARSING_ERROR while running my job on the code checked out up
>> to com
Hi npanj,
I'm seeing the same exception now on the Spark 1.1.0 release. Did you ever
get this figured out?
Andrew
On Thu, Aug 21, 2014 at 2:14 PM, npanj wrote:
> Hi All,
>
> I am getting PARSING_ERROR while running my job on the code checked out up
> to commit# db56f2df1b8027171da1b8d2571d1f2
Hi All,
I am getting PARSING_ERROR while running my job on the code checked out up
to commit# db56f2df1b8027171da1b8d2571d1f2ef1e103b6. I am running this job
on EC2.
Any idea if there is something wrong with my config?
Here is my config:
--
.set("spark.executor.extraJavaOptions", "-XX:+UseC
