hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3796) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits
Date Mon, 20 Feb 2012 06:45:38 GMT

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

Hitesh Shah commented on MAPREDUCE-3796:
----------------------------------------

@Vinod, true - had thought of that but for that to be done, I think we need to move the min/max
allocation configuration to be a global RM-level setting and not a scheduler-specific configuration
option. 
                
> Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation
limits 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3796
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3796
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Critical
>         Attachments: MR-3796.1.patch, MR-3796.2.patch, MR-3796.wip.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message