You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Akira Ajisaka (JIRA)" <ji...@apache.org> on 2017/06/12 09:35:00 UTC
[jira] [Commented] (MAPREDUCE-6697) Concurrent task limits should
only be applied when necessary
[ https://issues.apache.org/jira/browse/MAPREDUCE-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046378#comment-16046378 ]
Akira Ajisaka commented on MAPREDUCE-6697:
------------------------------------------
Mostly looks good to me. I have one question in the test code:
{code}
allocator.schedule();
allocator.schedule();
allocator.schedule();
{code}
why the method is called 3 times?
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org