[
https://issues.apache.org/jira/browse/MAPREDUCE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-901:
------------------------------------
Attachment: MAPREDUCE-901.patch
This is almost there, sans two important pieces:
# It looks like I need to change ReduceContext to take TaskMetrics in-lieu of
Counters.Counter for it's inputCounter; a change to a public api... sigh!
# As Devaraj noted, I need to fix JobInProgress to store the incoming
TaskMetrics values in it's Counters.
> 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: Arun C Murthy
> Fix For: 0.21.0
>
> Attachments: 901_1.patch, 901_1.patch, MAPREDUCE-901.patch,
> MAPREDUCE-901.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.
