hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3483) CapacityScheduler reserves container on same node as AM but can't ever use due to never enough avail memory
Date Tue, 15 Apr 2014 14:12:19 GMT

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

Thomas Graves updated MAPREDUCE-3483:
-------------------------------------

    Affects Version/s:     (was: 0.23.0)
                       2.3.0

> CapacityScheduler reserves container on same node as AM but can't ever use due to never
enough avail memory
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3483
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3483
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.3.0
>            Reporter: Thomas Graves
>            Assignee: Arun C Murthy
>
> Saw a case where a job was stuck trying to get reducers.  The issue is the capacity scheduler
reserved a container on the same node as the application master but there wasn't ever enough
memory to run the reducer on that node.  Node total memory was 8G, Reducer needed 8G, AM was
using 2G.  This particular job had 10 reducers and it was stuck waiting on the one because
the AM + reserved reducer memory was already over the queue limit.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message