hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6808) Log map attempts as part of shuffle handler audit log
Date Tue, 19 Sep 2017 14:11:00 GMT

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

Jason Lowe updated MAPREDUCE-6808:
----------------------------------
    Fix Version/s: 2.8.3
                   2.9.0

Thanks, [~pairg]!  I committed this to branch-2 and branch-2.8 as well.

> 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: 2.9.0, 3.0.0-alpha4, 2.8.3
>
>         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.4.14#64029)

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