[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685700#comment-13685700
]
Jason Lowe commented on MAPREDUCE-5311:
---------------------------------------
I'm OK with either faking the calculation with the RM config value read by the
AM *iff* mem-millis shows up very soon after 2.1-beta. A number of our users
use this counter value, and if it's missing we need another counter value to
point them to instead.
By "map slot-millis to mem-millis" what does that entail? I don't think a
direct mapping makes sense, as the units are totally different. Or are you
planning on doing something like dividing mem-millis by the min allocation from
the config to continue faking slot-millis?
> 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
