hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6209) Implement a heuristic to auto-size Java heap of MRAppMaster container
Date Fri, 16 Jan 2015 12:58:35 GMT

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

Karthik Kambatla commented on MAPREDUCE-6209:
---------------------------------------------

MAPREDUCE-5785 already does that. I believe Gera is proposing different AM container heap
sizes for jobs with few (10s) and many (100000s) map/reduce tasks. 

> Implement a heuristic to auto-size Java heap of MRAppMaster container
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6209
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6209
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster
>            Reporter: Gera Shegalov
>
> The size of Java heap required by the AM is linearly proportional to the size of the
MR job (number of mappers/splits and reducers). it would be nice if users did not have to
adjust the AM container size when transitioning from testing job on a small sample to a production
job on a full-scale dataset. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message