hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4683) Move the call to getMapCompletionEvents in ReduceTask.ReduceCopier.fetchOutputs to a separate thread
Date Fri, 12 Dec 2008 08:00:48 GMT

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

Devaraj Das updated HADOOP-4683:
--------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Jothi!

> Move the call to getMapCompletionEvents in ReduceTask.ReduceCopier.fetchOutputs to a
separate thread
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4683
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4683
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Jothi Padmanabhan
>             Fix For: 0.20.0
>
>         Attachments: hadoop-4683.patch
>
>
> The method ReduceTask.ReduceCopier.fetchOutputs makes a call to getMapCompletionEvents
every iteration of the loop. This should be moved out to a separate thread. This might slow
down the shuffle scheduler in some cases since there is a sleep inside the getMapCompletionEvents
method.

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


Mime
View raw message