[
https://issues.apache.org/jira/browse/MAPREDUCE-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838775#comment-15838775
]
Hudson commented on MAPREDUCE-6808:
-----------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11175 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11175/])
MAPREDUCE-6808. Log map attempts as part of shuffle handler audit log
(templedf: rev a7463b6c88f698950a2f326030261001aa51b35e)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java
> Log map attempts as part of shuffle handler audit log
> -----------------------------------------------------
>
> Key: MAPREDUCE-6808
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6808
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha1
> Reporter: Jonathan Eagles
> Assignee: Gergő Pásztor
> Fix For: 3.0.0-alpha3
>
> Attachments: MAPREDUCE-6808_v1.patch, MAPREDUCE-6808_v2.patch
>
>
> With the introduction tez, multiple unrelated reducers in the same job will
> have the same id. The audit log won't be able to distinguish which map
> attempt the reduce was fetching. This jira is to discuss the possibility to
> add map attempts logging to distinguish between the two.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
