[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740037#comment-13740037
]
Bikas Saha commented on MAPREDUCE-5311:
---------------------------------------
The uber problem seems that MR happens to be a special user that for historical
reasons has its fingers poked into all kinds of YARN internals and as such is
suffering when we close those gaps in YARN. Is there an issue with MR code
using the existing (and possible in future deprecated) min resource YARN
configuration for its internal calculations? That value was basically exposed
by YARN via the min API which we removed since we believed it wasnt relevant to
users. MR as a special user needs that info. How about we just get it from the
config directly.
> Replace SLOTS_MILLIS counters with MEM_MILLIS
> ---------------------------------------------
>
> 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
> Priority: Blocker
> Fix For: 2.1.0-beta
>
> 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
