[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683824#comment-13683824
]
Jason Lowe commented on MAPREDUCE-5311:
---------------------------------------
Seems reasonable if it's critical to remove MIN before 2.1, as I'm not sure how
else it could be computed. I could see yarn-site.xml for an application not
being consistent with the one used by the RM, which could lead to a bad
computation for the counter value. Consumers of the counter would need to be
aware that the slot was computed based on the AM's perception of a slot rather
than what the RM used.
Thoughts, [~acmurthy]? I know you had reservations earlier.
> 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
