Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1290792303.1208203145378.JavaMail.jira@brutus>
Date: Mon, 14 Apr 2008 12:59:05 -0700 (PDT)
From: "Runping Qi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3130) Shuffling takes too long to get the
 last map output.
In-Reply-To: <988740632.1206751104225.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588752#action_12588752 ] 

Runping Qi commented on HADOOP-3130:
------------------------------------


Overall looks good.

A minor point. Since UNIT_CONNECT_TIMEOUT  is private final, the following code segment seems redudant:
{code}
+      if (UNIT_CONNECT_TIMEOUT <= 0) {
+        throw new IOException("Invalid unit-timeout "
+                              + "[unit-timeout = " + UNIT_CONNECT_TIMEOUT 
+                              + " ms]");
+      } else {
{code}

> Shuffling takes too long to get the last map output.
> ----------------------------------------------------
>
>                 Key: HADOOP-3130
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3130
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Runping Qi
>            Assignee: Amar Kamat
>         Attachments: HADOOP-3130-v2.patch, HADOOP-3130-v2.patch, HADOOP-3130-v3.1.patch, HADOOP-3130-v3.patch, HADOOP-3130.patch, shuffling.log
>
>
> I noticed that towards the end of shufflling, the map output fetcher of the reducer backs off too aggressively.
> I attach a fraction of one reduce log of my job.
> Noticed that the last map output was not fetched in 2 minutes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.