[
https://issues.apache.org/jira/browse/HADOOP-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HADOOP-577.
----------------------------------
Resolution: Duplicate
This was fixed by HADOOP-492, which implemented per-task and per-job counters.
The default counters include bytes and records input and output. They are
printed on the console when the job completes. They are available as the job
runs via the http server. The times are available from the time stamps on the
progress messages and are available on the web/ui.
> Job tracker should collect detailed information about tasks and return it to
> the client
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-577
> URL: https://issues.apache.org/jira/browse/HADOOP-577
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Environment: all
> Reporter: arkady borkovsky
> Assigned To: Owen O'Malley
>
> Mapreduce driver should get detailed information about task execution -- at
> least at the end of the job so that it can be repoted to the user (stored in
> a "normal" or HDFS file, printed to the stdout, whatever).
> This information should include, at least:
> -- task execution start and end
> -- the number of record read and written
> -- the number of butes read and written
> for each task (for each attempt)
> It would also be nice to have this infromation while the job is running,
> updated at least when a task is started or ended.
> However, this is just "nice to have", while the final report is quite
> essential.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
