Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 270FD9A00 for ; Wed, 28 Dec 2011 12:01:54 +0000 (UTC) Received: (qmail 10077 invoked by uid 500); 28 Dec 2011 12:01:53 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 10044 invoked by uid 500); 28 Dec 2011 12:01:53 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 10036 invoked by uid 99); 28 Dec 2011 12:01:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2011 12:01:53 +0000 X-ASF-Spam-Status: No, hits=-2001.3 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2011 12:01:53 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 4BD1F12D99A for ; Wed, 28 Dec 2011 12:01:32 +0000 (UTC) Date: Wed, 28 Dec 2011 12:01:32 +0000 (UTC) From: "Sharad Agarwal (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <241730962.48414.1325073692311.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1108808318.29108.1322702259853.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3490) RMContainerAllocator counts failed maps towards Reduce ramp up MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176621#comment-13176621 ] Sharad Agarwal commented on MAPREDUCE-3490: ------------------------------------------- currently all bookkeeping and calculations in RMContainerAllocator are based on attempts not on tasks. there is one to one between attempt and container. completedMapPercent is currently completed map *attempts* percentage. I looked in more detail. we can simply change this to reflect completed map tasks percentage. All information is readily available there in Job. So we need not maintain these counts in RMContainerAllocator. Arun also mentioned this. I am attaching a patch which drastically simplify this, without the need to add new events. Also I have removed the completedMaps and completedReduces counts in RMContainerAllocator. Arun/Vinod - see if this make sense ? > RMContainerAllocator counts failed maps towards Reduce ramp up > -------------------------------------------------------------- > > Key: MAPREDUCE-3490 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3490 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am, mrv2 > Affects Versions: 0.23.0 > Reporter: Siddharth Seth > Assignee: Arun C Murthy > Priority: Blocker > Attachments: MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MAPREDUCE-3490.patch, MR-3490-alternate.patch > > > The RMContainerAllocator does not differentiate between failed and successful maps while calculating whether reduce tasks are ready to launch. Failed tasks are also counted towards total completed tasks. > Example. 4 failed maps, 10 total maps. Map%complete = 4/14 * 100 instead of being 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira