[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728327#comment-13728327
]
Alejandro Abdelnur commented on MAPREDUCE-5311:
-----------------------------------------------
[~acmurthy], per [~jlowe]'s comment above "so all that's left is to clarify
what will happen to slot-millis once mem-millis shows up." he does not seem
unhappy.
I think the problem we have at hand here is that there is a legacy metrics,
slots-millis, which does not make sense in YARN regardless what it returns 0 or
mem-millis. Anybody relying on this value coming from Hadoop 1 will get
something completely different to what was getting when running in Hadoop 1.
This means that if we make it disappear or we leave around returning the wrong
value (a funny mem-millis based on MIN config now), current users relying on it
will have to adjust how they see/process this value.
Because of that, I would say, we just bite the problem, and we make the
slot-millis counter to return 0 (or better -1), deprecate the constants, print
a warning when somebody uses this constant indicating the user to user look for
memory-millis (and eventually cpu-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: Sandy Ryza
> Attachments: MAPREDUCE-5311-1.patch, MAPREDUCE-5311.patch,
> 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
