You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Gergő Pásztor (JIRA)" <ji...@apache.org> on 2017/01/06 15:03:58 UTC
[jira] [Commented] (MAPREDUCE-6808) Log map attempts as part of
shuffle handler audit log
[ https://issues.apache.org/jira/browse/MAPREDUCE-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804722#comment-15804722 ]
Gergő Pásztor commented on MAPREDUCE-6808:
------------------------------------------
Sorry for the late reply, I attached a patch.
> 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
> Attachments: MAPREDUCE-6808_v1.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org