[
https://issues.apache.org/jira/browse/MAPREDUCE-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065819#comment-16065819
]
Hudson commented on MAPREDUCE-6697:
-----------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11938 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11938/])
MAPREDUCE-6697. Concurrent task limits should only be applied when (aajisaka:
rev a5c0476a990ec1e7eb34ce2462a45aa52cc1350d)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java
> Concurrent task limits should only be applied when necessary
> ------------------------------------------------------------
>
> Key: MAPREDUCE-6697
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6697
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.7.0
> Reporter: Jason Lowe
> Assignee: Nathan Roberts
> Attachments: MAPREDUCE-6697-v1.patch
>
>
> The concurrent task limit feature should only adjust the ANY portion of the
> AM heartbeat ask when a limit is truly necessary, otherwise extraneous
> containers could be allocated by the RM to the AM adding some overhead to
> both. Specifying a concurrent task limit that is beyond the total number of
> tasks in the job should be the same as asking for no limit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
