hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siqi Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4818) Easier identification of tasks that timeout during localization
Date Tue, 07 Oct 2014 18:45:35 GMT

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

Siqi Li updated MAPREDUCE-4818:
-------------------------------
    Attachment: MAPREDUCE-4818.v4.patch

> Easier identification of tasks that timeout during localization
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-4818
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4818
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am
>    Affects Versions: 0.23.3, 2.0.3-alpha
>            Reporter: Jason Lowe
>            Assignee: Siqi Li
>              Labels: usability
>         Attachments: MAPREDUCE-4818.v1.patch, MAPREDUCE-4818.v2.patch, MAPREDUCE-4818.v3.patch,
MAPREDUCE-4818.v4.patch
>
>
> When a task is taking too long to localize and is killed by the AM due to task timeout,
the job UI/history is not very helpful.  The attempt simply lists a diagnostic stating it
was killed due to timeout, but there are no logs for the attempt since it never actually got
started.  There are log messages on the NM that show the container never made it past localization
by the time it was killed, but users often do not have access to those logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message