hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1413) Improve logging of progress/errors in the job and task trackers
Date Mon, 15 Feb 2010 10:47:27 GMT

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

Steve Loughran commented on MAPREDUCE-1413:

The log calls aren't logging the _whole_ exception twice
# The log message includes the toString() value of the exception, normally the value of getMessage(),
though that can be changed. This message doesn't include the stack trace
# The second parameter passes in the raw exception chain with full stack trace. It is up to
the log engine what it does with that; printing out the stack trace in text is one option,
but I know of others (discard, save the fault as an XML-parseable). This is why log(text,Throwable)
is the recommended way to log faults in all the main java log frameworks.
# Sometimes I've seen loggers not log the toString() value of the exception passed in as param
#2, which is less than ideal if you are trying to track down a problem and all you have are
the logs.
# Therefore, I do think what I've done is the best tactic to producing logs that are human
and machine readable.
# Will check out the javadoc error and submit a patch that corrects that.

> 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.

View raw message