hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3796) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits
Date Sun, 26 Feb 2012 07:38:49 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated MAPREDUCE-3796:
-----------------------------------------------

        Fix Version/s: 0.23.2
     Target Version/s:   (was: 0.24.0, 0.23.1)
    Affects Version/s:     (was: 0.24.0)
               Status: Open  (was: Patch Available)

bq.  I think we need to move the min/max allocation configuration to be a global RM-level
setting
Sure, +1. I had done that as part of MAPREDUCE-3812, but that ticket needs more effort. Would
favor getting that part in here.
                
> 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
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Critical
>             Fix For: 0.23.2
>
>         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