[
https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738516#comment-13738516
]
Alejandro Abdelnur commented on MAPREDUCE-5311:
-----------------------------------------------
[~acmurthy], it seems we are talking pass each other here.
* 1. SLOT_MILLIS does make sense in YARN. yes/no?
* 2. We need to redefine what SLOT_MILLIS means/reports in YARN. yes/no?
Are we in agreement that the answers to these questions is #1 NO and #2 YES.
If we are in agreement, then we have to see how to address this in the least
disruptive way.
Sandy's latest proposal suggests we do the following:
* Introduce the concept of CONTAINER_MILLIS (regardless of the container size)
* Deprecate SLOT_MILLIS and map it to report CONTAINER_MILLIS
And we could later augment this with additional counters:
* Introduce the concept of MEMORY_MILLIS
* Introduce the concept of CPU_MILLIS
> 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
