hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gergő Pásztor (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6808) Log map attempts as part of shuffle handler audit log
Date Fri, 06 Jan 2017 15:01:06 GMT

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

Gergő Pásztor updated MAPREDUCE-6808:
    Affects Version/s: 3.0.0-alpha1
               Status: Patch Available  (was: Open)

> 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

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message