hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-479) Add reduce ID to shuffle clienttrace
Date Mon, 24 Aug 2009 03:54:59 GMT

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

Chris Douglas updated MAPREDUCE-479:
------------------------------------

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

+1

I committed this. Thanks Jiaqi!

> Add reduce ID to shuffle clienttrace
> ------------------------------------
>
>                 Key: MAPREDUCE-479
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-479
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.21.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-6013.patch, MAPREDUCE-479-1.patch, MAPREDUCE-479-2.patch,
MAPREDUCE-479-3.patch, MAPREDUCE-479-4.patch, MAPREDUCE-479.patch
>
>
> Current clienttrace messages from shuffles note only the destination map ID but not the
source reduce ID. Having both source and destination ID of each shuffle enables full tracing
of execution. 

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