[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679540#comment-13679540
]
Jason Lowe commented on MAPREDUCE-5311:
---------------------------------------
Many of our users leverage the slot millis counter as a metric for cluster
utilization for jobs. While I agree the "slot" concept is confusing in
0.23/2.x, our users need some counter to track their utilization. If these
counters are deprecated, we need to create something more appropriate to
replace them so users can still track cluster utilization.
I would like to see some sort of "resource-millis" counters so we can track the
amount of time a job was consuming a particular cluster resource and how much
of that resource during that time. So memory would be tracked via MB-millis or
GB-millis, CPU could be core-millis or vcore-millis, etc. It would be great if
this was tracked by YARN directly and available regardless of the app framework
used, but that's a much bigger change.
> Remove slot millis computation logic and deprecate counter constants
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-5311
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5311
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 2.0.4-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: MAPREDUCE-5311.patch
>
>
> Per discussion in MAPREDUCE-5310 and comments in the code we should remove
> all the related logic and just leave the counter constant for backwards
> compatibility and deprecate the counter constants.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
