hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2456) Show the reducer taskid and map/reduce tasktrackers for "Failed fetch notification #_ for task attempt..." log messages
Date Wed, 11 May 2011 14:57:47 GMT

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

Hudson commented on MAPREDUCE-2456:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #676 (See [https://builds.apache.org/hudson/job/Hadoop-Mapreduce-trunk/676/])
    MAPREDUCE-2456. Log the reduce taskID and associated TaskTrackers with
failed fetch notifications in the JobTracker log.
Contributed by Jeffrey Naisbitt


> 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.20.205.0, 0.23.0
>
>         Attachments: MAPREDUCE-2456-0.20s.patch, MAPREDUCE-2456-trunk.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

Mime
View raw message