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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/05/16 19:53:12 UTC

[jira] [Created] (MAPREDUCE-6697) Concurrent task limits should only be applied when necessary

Jason Lowe created MAPREDUCE-6697:
-------------------------------------

             Summary: 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


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.3.4#6332)

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