Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3FF4611202 for ; Thu, 17 Jul 2014 21:40:07 +0000 (UTC) Received: (qmail 45192 invoked by uid 500); 17 Jul 2014 21:40:05 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 45101 invoked by uid 500); 17 Jul 2014 21:40:05 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 45088 invoked by uid 99); 17 Jul 2014 21:40:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 21:40:05 +0000 Date: Thu, 17 Jul 2014 21:40:05 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-2980) slow reduce copies - map output locations not being fetched even when map complete 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/HADOOP-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-2980. -------------------------------------- Resolution: Incomplete I'm going to close this as stale. If people are still seeing this as an issue, they should file a new jira with new data! > slow reduce copies - map output locations not being fetched even when map complete > ---------------------------------------------------------------------------------- > > Key: HADOOP-2980 > URL: https://issues.apache.org/jira/browse/HADOOP-2980 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 0.15.3 > Reporter: Joydeep Sen Sarma > > maps are long finished. reduces are stuck looking for map locations. they make progress - but slowly. it almost seems like they get new map locations every minute or so: > 2008-03-07 18:50:52,737 INFO org.apache.hadoop.mapred.ReduceTask: task_200803041231_3586_r_000021_0 done copying task_200803041231_3586_m_004620_0 output from hadoop082.sf2p.facebook.com.. > 2008-03-07 18:50:53,733 INFO org.apache.hadoop.mapred.ReduceTask: task_200803041231_3586_r_000021_0: Got 0 new map-outputs & 0 obsolete map-outputs from tasktracker and 0 map-outputs from previous failures > 2008-03-07 18:50:53,733 INFO org.apache.hadoop.mapred.ReduceTask: task_200803041231_3586_r_000021_0 Got 0 known map output location(s); scheduling... > ... > 2008-03-07 18:51:49,767 INFO org.apache.hadoop.mapred.ReduceTask: task_200803041231_3586_r_000021_0 Got 50 known map output location(s); scheduling... > 2008-03-07 18:51:49,767 INFO org.apache.hadoop.mapred.ReduceTask: task_200803041231_3586_r_000021_0 Scheduled 41 of 50 known outputs (0 slow hosts and 9 dup hosts) > they get about 50 locations at a time and this 1 minute delay pattern is surprisingly common .. -- This message was sent by Atlassian JIRA (v6.2#6252)