hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3427) In ReduceTask::fetchOutputs, wait for result can be improved slightly
Date Mon, 30 Jun 2008 22:02:44 GMT

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

Robert Chansler updated HADOOP-3427:

    Release Note: Changed shuffle scheduler policy to wait for notifications from shuffle
threads before scheduling more.  (was: Improves the shuffle scheduler. It now waits for notifications
from shuffle threads when it has scheduled enough, before scheduling more.)

> 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.

View raw message