[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated MAPREDUCE-1265: Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) I just committed this. Thanks Scott! > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Status: Patch Available (was: Open) > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Status: Open (was: Patch Available) > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Description: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__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. was: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 failed to report status for 601 seconds. Killing! When we want to debug a machine for example, a blacklisted node. 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 cauces this error. This way we can just grep the hostname to quickly find all the relevant error message. > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Description: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 failed to report status for 601 seconds. Killing! When we want to debug a machine for example, a blacklisted node. 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 cauces this error. This way we can just grep the hostname to quickly find all the relevant error message. was: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 failed to report status for 601 seconds. Killing! When we want to debug a machine for example, a blacklisted node. We have to use the task attempt id to find these information. This is not very convenient. It will be nice if we can also log the tasktracker which cauces this error. This way we can just grep the hostname to quickly find all the relevant error message. > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 > failed to report status for 601 seconds. Killing! > When we want to debug a machine for example, a blacklisted node. > 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 cauces 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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Fix Version/s: 0.22.0 Affects Version/s: 0.22.0 Status: Patch Available (was: Open) > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 > failed to report status for 601 seconds. Killing! > When we want to debug a machine for example, a blacklisted node. > We have to use the task attempt id to find these information. This is not > very convenient. > It will be nice if we can also log the tasktracker which cauces 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.
[jira] Updated: (MAPREDUCE-1265) Include tasktracker name in the task attempt error log
[ https://issues.apache.org/jira/browse/MAPREDUCE-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1265: -- Description: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 failed to report status for 601 seconds. Killing! When we want to debug a machine for example, a blacklisted node. We have to use the task attempt id to find these information. This is not very convenient. It will be nice if we can also log the tasktracker which cauces this error. This way we can just grep the hostname to quickly find all the relevant error message. was: 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: Java heap space 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_2009__m_000478_0: Task attempt_2009__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. Summary: Include tasktracker name in the task attempt error log (was: Include jobId and hostname in the task attempt error log) > 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 >Reporter: Scott Chen >Assignee: Scott Chen >Priority: Trivial > 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_2009__r_09_1: Error: java.lang.OutOfMemoryError: > Java heap space > 2009-xx-xx 22:53:53,146 INFO org.apache.hadoop.mapred.TaskInProgress: Error > from attempt_2009__m_000478_0: Task attempt_2009__m_000478_0 > failed to report status for 601 seconds. Killing! > When we want to debug a machine for example, a blacklisted node. > We have to use the task attempt id to find these information. This is not > very convenient. > It will be nice if we can also log the tasktracker which cauces 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.
