[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738620#comment-13738620
]
Sandy Ryza commented on MAPREDUCE-5311:
---------------------------------------
As slots no longer exist in MR2, we cannot avoid breaking compatibility for
some existing applications.
Keeping SLOTS_MILLIS as it is will break compatibility for the majority of MR1
clusters.
Defining SLOTS_MILLIS to be the same as CONTAINER_MILLIS will break
compatibility for the minority of clusters that both used the
mapred.cluster.map.memory.mb property in MR1 and chose to configure memory in
MR2 in a way that exactly lines up with slots in MR1 (i.e. setting
yarn.scheduler.minimum-allocation-mb to exactly the same as
mapred.cluster.map.memory.mb, which is often not the right choice).
> 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
