[
https://issues.apache.org/jira/browse/MAPREDUCE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858791#action_12858791
]
Amareshwari Sriramadasu commented on MAPREDUCE-1219:
----------------------------------------------------
bq. shouldn't jobtracker publish its own metrics and not include job level
details? Also, users can obtain the counters using different API. So can we
remove the job level metrics aka counters from JobTracker metrics?
+1 we should remove the Job level metrics from JobTracker metrics.
Attached patch just removes the jobMetrics from doUpdates(). Shall we remove
the collection part also from JobInProgress code, because we don't update
anymore?
> JobTracker Metrics causes undue load on JobTracker
> --------------------------------------------------
>
> Key: MAPREDUCE-1219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1219
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Jothi Padmanabhan
> Assignee: Amareshwari Sriramadasu
> Attachments: MAPREDUCE-1219.patch, patch-1219-ydist.txt
>
>
> JobTrackerMetricsInst.doUpdates updates job-level counters of all running
> jobs into JobTracker's metrics causing very bad performance and hampers
> heartbeats. Since Job level metrics are better served by JobHistory, it may
> be a good idea to remove these from the metrics framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
