[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683930#comment-13683930
]
Alejandro Abdelnur commented on MAPREDUCE-5311:
-----------------------------------------------
How about?
*for 2.1-beta:*
* we change the calculation to use the MIN value from the local config
(typically people use the in the clients the same confs as in the cluster)
* we get rid of the MIN from the Yarn Client API
*for the next release:*
* introduce mem-millis and vcores-millis using allocation info
* map slot-millis to mem-millis
* deprecate slot-millis counter names
If folks agree I can put a patch changing the calculation to use the MIN value
from the local config
> 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