hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5311) Remove slot millis computation logic and deprecate counter constants
Date Fri, 14 Jun 2013 21:19:21 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683797#comment-13683797
] 

Alejandro Abdelnur commented on MAPREDUCE-5311:
-----------------------------------------------

I was hoping to get rid of it so we can go ahead with YARN-787 which is a YARN proto/API change
before 2.1. Would then be acceptable to do the current calculation picking up MIN from the
yarn configuration of the client? If so, I can do that in YARN-787 as part of removing MIN.
and we make this one to be blocked by a new JIRA that introduces MEM-millis and CPU-millis.
Thoughts?
                
> 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: Alejandro Abdelnur
>         Attachments: 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

Mime
View raw message