Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 30 May 2013 09:31:19 +0000 (UTC)
From: "PengZhang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12649644.1369728805180.40114.1369906279974@arcas>
In-Reply-To: <JIRA.12649644.1369728805180@arcas>
References: <JIRA.12649644.1369728805180@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5279) mapreduce scheduling deadlock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

PengZhang updated MAPREDUCE-5279:
---------------------------------

    Attachment: MAPREDUCE-5279.patch
    
> mapreduce scheduling deadlock
> -----------------------------
>
>                 Key: MAPREDUCE-5279
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5279
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, scheduler
>    Affects Versions: 2.0.3-alpha
>            Reporter: PengZhang
>         Attachments: MAPREDUCE-5279.patch
>
>
> YARN-2 imported cpu dimension scheduling, but MR RMContainerAllocator doesn't take into account virtual cores while scheduling reduce tasks.
> This may cause more reduce tasks to be scheduled because memory is enough. And on a small cluster, this will end with deadlock, all running containers are reduce tasks but map phase is not finished. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira