hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ed Mazur <ma...@cs.umass.edu>
Subject Re: Map output compression leads to JVM crash (0.20.0)
Date Mon, 26 Oct 2009 19:25:35 GMT
Err, disregard that.

$ cat /proc/version
Linux version 2.6.9-89.0.9.plus.c4smp (mockbuild@builder10.centos.org)
(gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)) #1 SMP Mon Aug 24
09:06:26 EDT 2009

Ed

On Mon, Oct 26, 2009 at 3:23 PM, Ed Mazur <mazur@cs.umass.edu> wrote:
> $ cat /etc/*-release
> CentOS release 4.5 (Final)
> Rocks release 4.3 (Mars Hill)
>
> Ed
>
> On Mon, Oct 26, 2009 at 11:21 AM, Todd Lipcon <todd@cloudera.com> wrote:
>> What Linux distro are you running? It seems vaguely possible that you're
>> using some incompatible library versions compared to what everyone else has
>> tested libhadoop with.
>>
>> -Todd
>>
>> On Sun, Oct 25, 2009 at 8:36 PM, Ed Mazur <mazur@cs.umass.edu> wrote:
>>>
>>> I'm having problems on 0.20.0 when map output compression is enabled.
>>> Map tasks complete (TaskRunner: Task 'attempt_*' done), but it looks
>>> like the JVM running the task crashes immediately after.  Here's the
>>> TaskTracker log:
>>>
>>> java.io.IOException: Task process exit with nonzero status of 134.
>>>    at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:418)
>>>
>>> An error per task attempt.  Each also produces a JRE error report file:
>>>
>>> http://pastebin.com/f590087f0
>>>
>>> This was using DefaultCodec.  I observed similar results with GzipCodec.
>>>
>>> Ed Mazur
>>
>>
>

Mime
View raw message