[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739629#comment-13739629
]
Arun C Murthy commented on MAPREDUCE-5311:
------------------------------------------
I'm glad we are coming around to understand we can break existing users of
SLOT_MILLIS.
I wasn't thrilled about using configs and I'm even more leery of adding new
configs to track existing configs in RM. This can lead to all sorts of
configuration-error hell with mismatch in configs b/w YarnConfiguration and
MRConf. I'm against getting into that sort of situations.
A much simpler approach is to re-introduce a LimitedPrivate
RegisterApplicationMasterResponse.getMinimumResourceCapability as described
here (http://bit.ly/18uA8zj). This would revert some part of YARN-787.
> 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
