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 Fri, 07 Jun 2013 22:50:21 GMT

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

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

On slot minis, then we should remove all the related logic and just leave the counter constant
for backwards compatibility and deprecating the constant. Better return zero than some gibberish,
I'll open a JIRA and post patch for it. 
                
> 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