hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2125) Put map-reduce framework counters to JobTrackerMetricsInst
Date Wed, 03 Nov 2010 18:10:26 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927926#action_12927926
] 

Luke Lu commented on MAPREDUCE-2125:
------------------------------------

bq. I think adding one getJobCounter() for the entire lifecycle of a job should be allowed.
If this is not doable, why should we need this method getJobCounter()?

The problem is that many of the intermediate jobs don't need the additional getJobCounter
call. If you put it in the default instrumentation class, it becomes mandatory additional
expensive call for every job. I'd be more comfortable if you provide a way to turn it off,
preferably by default.

> Put map-reduce framework counters to JobTrackerMetricsInst
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-2125
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2125
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.22.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-2125-v2.txt, MAPREDUCE-2125.txt
>
>
> We have lots of useful information in the framework counters including #spills, filesystem
read and write.
> It will be nice to put them all in the jobtracker metrics to get a global view of all
these numbers.

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