hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-92) Error Reporting/logging in MapReduce
Date Tue, 21 Mar 2006 21:07:20 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-92?page=comments#action_12371296 ] 

Mahadev konar commented on HADOOP-92:

It could be done with a logs directory in output_dir. So, the output_dir/logs/tasks/  would
contain all the information per task (a file per task). This file would contain information
like -- machine name, start time, end time, result status, error messages. Also, there should
be a file per job  output_dir/logs/job_id.log. This file would contains job specific data
-- no of mapreduce tasks that were running at some time, number of machines it was running
on, and the start time and end time of the job. This log could also contain information on
which of the task failed, so that the user can take a look at the respective task log to know
why it failed.

> Error Reporting/logging in MapReduce
> ------------------------------------
>          Key: HADOOP-92
>          URL: http://issues.apache.org/jira/browse/HADOOP-92
>      Project: Hadoop
>         Type: Bug
>   Components: mapred
>     Reporter: Mahadev konar
>     Priority: Minor

> Currently Mapreduce does not tell you which machine failed to execute the task. Also,
it would be nice to have features wherein there is a log report with each job, saying the
number of tasks it ran (reporting which one failed and on which machine, listing any error
information it can)  with  the start/end/execute time of each task. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message