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-5310) MRAM should not normalize allocation request capabilities
Date Mon, 10 Jun 2013 17:16:21 GMT

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

Alejandro Abdelnur commented on MAPREDUCE-5310:
-----------------------------------------------

[~acmurthy], that is what the current patch does, it divides the requested memory by the minimum
memory constant and the ceils it. We can decide on removing or improving this calculation
in MAPREDUCE-5311. 

Anything else in this patch or is it good to go?
                
> MRAM should not normalize allocation request capabilities
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-5310
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5310
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>    Affects Versions: 2.0.4-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: MAPREDUCE-5310.patch
>
>
> The MRAM is assuming knowledge of the scheduler internals to normalize allocation request
capabilities.
> Per discussions in YARN-689 and YARN-769 it should not do that.

--
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