[
https://issues.apache.org/jira/browse/MAPREDUCE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030767#comment-13030767
]
Patricio Echague commented on MAPREDUCE-5:
------------------------------------------
> If these messages are harmful, then we need to give a better message.
> If these messages aren't harmful, then we shouldn't be throwing a java
> exception.
+1
> Shuffle's getMapOutput() fails with EofException, followed by
> IllegalStateException
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.2
> Environment: Sun Java 1.6.0_13, OpenSolaris, running on a SunFire
> 4150 (x64) 10 node cluster
> Reporter: George Porter
>
> During the shuffle phase, I'm seeing a large sequence of the following
> actions:
> 1) WARN org.apache.hadoop.mapred.TaskTracker:
> getMapOutput(attempt_200905181452_0002_m_000010_0,0) failed :
> org.mortbay.jetty.EofException
> 2) WARN org.mortbay.log: Committed before 410
> getMapOutput(attempt_200905181452_0002_m_000010_0,0) failed :
> org.mortbay.jetty.EofException
> 3) ERROR org.mortbay.log: /mapOutput java.lang.IllegalStateException:
> Committed
> The map phase completes with 100%, and then the reduce phase crawls along
> with the above errors in each of the TaskTracker logs. None of the
> tasktrackers get lost. When I run non-data jobs like the 'pi' test from the
> example jar, everything works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
