Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1316917681.1212659985222.JavaMail.jira@brutus>
Date: Thu, 5 Jun 2008 02:59:45 -0700 (PDT)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3427) In ReduceTask::fetchOutputs, wait for
 result can be improved slightly
In-Reply-To: <776736020.1211374795666.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-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-3427:
--------------------------------

    Status: Open  (was: Patch Available)

Cancelling patch due to conflicts with trunk

> In ReduceTask::fetchOutputs, wait for result can be improved slightly
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-3427
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3427
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>             Fix For: 0.18.0
>
>         Attachments: 3427.3.patch, 3427.patch, 3427.patch, 3427.patch
>
>
> The getCopyResult call in ReduceTask::fetchOutputs waits for 2 seconds if the results list is empty. This can be improved to wait only when sufficient number of fetches (above a certain threshold) have been scheduled. The threshold should ensure that all the fetcher threads would be busy enough, and in this case, the call to getCopyResult would return only when a fetcher thread wakes it up.

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