[
https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787235#action_12787235
]
Scott Chen commented on MAPREDUCE-1265:
---------------------------------------
This one changes only contents of the log. So there is no unit test included.
> Include tasktracker name in the task attempt error log
> ------------------------------------------------------
>
> Key: MAPREDUCE-1265
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1265
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.22.0
> Reporter: Scott Chen
> Assignee: Scott Chen
> Priority: Trivial
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1265-v2.patch, MAPREDUCE-1265.patch
>
>
> When task attempt receive an error, TaskInProgress will log the task attempt
> id and diagnosis string in the JobTracker log.
> Ex:
> 2009-xx-xx 23:50:45,994 INFO org.apache.hadoop.mapred.TaskInProgress: Error
> from attempt_2009xxxx_xxxx_r_000009_1: Error: java.lang.OutOfMemoryError:
> Java heap space
> 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error
> from attempt_2009xxxx_xxxx_m_000478_0: Task attempt_2009xxxx_xxxx_m_000478_0
> failed to report status for 601 seconds. Killing!
> When we want to debug a machine for example, a node has been blacklisted in
> the past few days.
> We have to use the task attempt id to find the TT. This is not very
> convenient.
> It will be nice if we can also log the tasktracker which causes this error.
> This way we can just grep the hostname to quickly find all the relevant error
> message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
