hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-481) Hadoop mapred metrics should include per job input/output statistics rather than per-task statistics
Date Fri, 09 Feb 2007 22:12:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471847
] 

Nigel Daley commented on HADOOP-481:
------------------------------------

FWIW, HADOOP-954 has changed all task related statistics to be per user (the user that submitted
the job).  Currently, these counters are aggregated per user:

  map_input_bytes 
  map_input_records
  map_output_bytes
  map_output_records
  shuffle_input_bytes
  reduce_input_records
  reduce_output_records


> Hadoop mapred metrics should include per job input/output statistics rather than per-task
statistics
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-481
>                 URL: https://issues.apache.org/jira/browse/HADOOP-481
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred, metrics
>    Affects Versions: 0.6.0
>            Reporter: Milind Bhandarkar
>         Assigned To: Milind Bhandarkar
>            Priority: Minor
>         Attachments: reports.patch
>
>
> Currently hadoop reports metrics such as input bytes, input records, etc on per-task
basis. Accurate aggregation of these metrics is required at the job-level and reporting should
be done on a per-job basis.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message