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 Mon, 10 Jun 2013 17:24:21 GMT

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

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

[~acmurthy], [~jlowe], [~sseth]. If I'm getting correct the current logic we are using the
memory requested by the AM for the task, not the allocated (RM scheduler normalized) memory.


As it seems users are relying on this we could:

* Use the memory from the container allocation for the calculation. This will give a more
correct idea of the 'real' utilization without exposing the normalization logic to the MRAM.
This effectively would be memory-millis.
* Do the same for vcore-millis.
* Add memory-millis and vcore-millis counters and deprecate slot-millis keeping it wired to
memory-millis.

If we agree on this, I'll repurpose this JIRA to do so.
                
> 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