You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Nick Jones (JIRA)" <ji...@apache.org> on 2011/08/28 16:08:39 UTC

[jira] [Commented] (MAPREDUCE-2389) Spurious EOFExceptions reading SpillRecord index files

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092488#comment-13092488 ] 

Nick Jones commented on MAPREDUCE-2389:
---------------------------------------

I also have the same problem on CDH3u0 and was able to workaround it by reverting Jetty 6.1.26 to Jetty 6.1.14.

Environment:
Ubuntu 10.04 x64
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)

> Spurious EOFExceptions reading SpillRecord index files
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-2389
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2389
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>    Affects Versions: 0.22.0
>         Environment: Seen on RHEL 5.5, RHEL 6.0, local dirs on ext3, Java 6u20 and 6u24
>            Reporter: Todd Lipcon
>            Priority: Critical
>         Attachments: stap-output.txt
>
>
> In large jobs, I see around 1 shuffle fetch out of every million fetches fail with an EOFException reading the SpillRecord index file. After lots of investigation, including systemtap, it looks like the read() syscall is actually returning a premature "0" result for no reason, so this is likely a kernel or filesystem bug which is exacerbated by some workload the TT does.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira