hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chang Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5002) AM could potentially allocate a reduce container to a map attempt
Date Thu, 10 Sep 2015 18:57:47 GMT

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

Chang Li commented on MAPREDUCE-5002:

Thanks [~jlowe] for review! Have reworked my unit test. Please help review the updated patch.

> AM could potentially allocate a reduce container to a map attempt
> -----------------------------------------------------------------
>                 Key: MAPREDUCE-5002
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5002
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.0.3-alpha, 0.23.7, 2.7.0
>            Reporter: Jason Lowe
>            Assignee: Chang Li
>         Attachments: MAPREDUCE-5002.1.patch, MAPREDUCE-5002.2.patch, MAPREDUCE-5002.2.patch,
MAPREDUCE-5002.3.patch, MAPREDUCE-5002.4.patch
> As discussed in MAPREDUCE-4982, after MAPREDUCE-4893 it is theoretically possible for
the AM to accidentally assign a reducer container to a map attempt if the AM doesn't find
a reduce attempt actively looking for the container (e.g.: the RM accidentally allocated too
many reducer containers).

This message was sent by Atlassian JIRA

View raw message