hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6808) Log map attempts as part of shuffle handler audit log
Date Mon, 19 Dec 2016 17:32:58 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761776#comment-15761776
] 

Jonathan Eagles commented on MAPREDUCE-6808:
--------------------------------------------

Agree with [~kshukla]. Having this JIRA fixed would help me to better support tez. Any chance
of a patch coming soon, [~haibochen], [~pairg]?

> 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
>            Reporter: Jonathan Eagles
>            Assignee: Gergő Pásztor
>
> 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


Mime
View raw message