hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6697) Concurrent task limits should only be applied when necessary
Date Wed, 12 Jul 2017 22:40:00 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Konstantin Shvachko updated MAPREDUCE-6697:
    Attachment: MAPREDUCE-6697-branch-2.7.001.patch

The patch applies cleanly to 2.7, and TestRMContainerAllocator passes.
Let's just reattach the same patch for a full Jenkins run on branch-2.7.

> 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
>             Fix For: 2.9.0, 3.0.0-alpha4
>         Attachments: MAPREDUCE-6697-branch-2.7.001.patch, MAPREDUCE-6697-branch-2.8.001.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

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

View raw message