[ https://issues.apache.org/jira/browse/MAPREDUCE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732391#action_12732391 ]
Chris Douglas commented on MAPREDUCE-479: ----------------------------------------- As I said earlier, if you wanted to replace the reduce parameter with the attempt id- and extract the former from the latter- I wouldn't oppose it. What bothers me is that, other than logging it to the clienttrace on behalf of a possible downstream tool, the parameter serves no functional purpose to map/reduce; it is likely to be "optimized" away. If you elect to do this, you should also add a comment explaining why the full attempt id is included in the request. > 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.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.