[
https://issues.apache.org/jira/browse/MAPREDUCE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834105#action_12834105
]
Chris Douglas commented on MAPREDUCE-1413:
------------------------------------------
That seems tautological to me: if one's logger is configured to not print the
exception, then it is unavailable in the logs. But as a practical
accommodation, I see your point. OK.
Instead of defining {{toString()}} for the TaskTracker, could this just print
the relevant information in offerService? Or are you using that in the service
lifecycle branch somehow?
> Improve logging of progress/errors in the job and task trackers
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-1413
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1413
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tasktracker
> Affects Versions: 0.22.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1413.patch
>
>
> I have code that improves the logging of the trackers as they start stop and
> fail, through
> # More logging of events
> # including exception strings and stacks when things go wrong
> People's whose JTs and TTs aren't behaving may appreciate this
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
