[
https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Chen updated MAPREDUCE-1265:
----------------------------------
Attachment: (was: MAPREDUCE-1265.patch)
> Include jobId and hostname 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
> Reporter: Scott Chen
> Assignee: Scott Chen
> Priority: Trivial
>
> 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 or a job. We have to use the task attempt id
> to find these information.
> It will be much more convenient if we can just log them together.
> This way we can just grep the jobId or 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.
