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

Jeffrey Naisbitt commented on MAPREDUCE-2456:
---------------------------------------------

No tests were included since this is basically just adding information to log 
messages.

Here are the test-patch results from the 0.20-security branch.  The javadoc and 
Eclipse classpath errors are unrelated to this bug since they appear in the 
0.20-security branch without my changes. 
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new or 
modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec]
[exec] -1 javadoc. The javadoc tool appears to have generated 1 warning 
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac 
compiler warnings.
[exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs 
warnings. [exec]
[exec] -1 Eclipse classpath. The patch causes the Eclipse classpath to differ 
from the contents of the lib directories. [exec] [exec]
[exec]
[exec]

> Show the reducer taskid and map/reduce tasktrackers for "Failed fetch 
> notification #_ for task attempt..." log messages
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2456
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2456
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.20.204.0
>            Reporter: Jeffrey Naisbitt
>            Assignee: Jeffrey Naisbitt
>            Priority: Trivial
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2456-0.20s.patch, MAPREDUCE-2456-trunk.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This jira is to provide more useful log information for debugging the "Too 
> many fetch-failures" error.
> Looking at the JobTracker node, we see messages like this:
> "2010-12-14 00:00:06,911 INFO org.apache.hadoop.mapred.JobInProgress: Failed 
> fetch notification #8 for task
> attempt_201011300729_189729_m_007458_0".
> I would be useful to see which reducer is reporting the error here.
> So, I propose we add the following to these log messages:
>   1. reduce task ID
>   2. TaskTracker nodenames for both the mapper and the reducer

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

Reply via email to