hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6696) Add a configuration to limit the number of map tasks allowed per job.
Date Tue, 17 May 2016 23:33:13 GMT

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

Jian He commented on MAPREDUCE-6696:
------------------------------------

I think the MRJobConfig.NUM_MAPS is giving a hint about, not the actual, number of maps.
Btw, seems JobImpl#checkTaskLimits was the very initial code for the task limit. I guess it
was removed when YARN got created based on git history

> Add a configuration to limit the number of map tasks allowed per job.
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6696
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6696
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: job submission
>    Affects Versions: 2.8.0
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>         Attachments: MAPREDUCE-6696.000.patch, MAPREDUCE-6696.001.patch, MAPREDUCE-6696.002.patch
>
>
> Add a configuration "mapreduce.job.max.map" to limit the number of map tasks allowed
per job. It will be useful for Hadoop admin to save Hadoop cluster resource by preventing
users from submitting big mapreduce jobs. A mapredeuce job with too many mappers may fail
with OOM after running for long time. It will be a big waste.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message