[
https://issues.apache.org/jira/browse/MAPREDUCE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747133#action_12747133
]
Arun C Murthy commented on MAPREDUCE-901:
-----------------------------------------
Hmm... at the risk of sounding completely lame, I can't seem to find the
definition of TaskMetrics or TaskCounters - did you forget to do included that
in the patch?
>From the description it seems like TaskMetrics is related to Counters, maybe I
>should wait to see the patch - anyway I was hoping TaskMetrics would be a
>Writable and isn't related to Counters at all.
> Move Framework Counters into a TaskMetric structure
> ---------------------------------------------------
>
> Key: MAPREDUCE-901
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-901
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 0.21.0
> Reporter: Owen O'Malley
> Assignee: Devaraj Das
> Fix For: 0.21.0
>
> Attachments: 901_1.patch
>
>
> I think we should move all of the Counters that the framework updates into a
> single class called TaskMetrics. TaskMetrics would have specific fields for
> each of the metrics like input records, input bytes, output records, etc.
> It would both reduce the serialized size of the heartbeats (by shrinking the
> Counters down to just the user's counters) and decrease the latency for
> updates to the JobTracker (since Counters are sent at most 1/minute instead
> of 1/heartbeat).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
