hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-4818) Easier identification of tasks that timeout during localization
Date Thu, 22 Nov 2012 02:04:58 GMT
Jason Lowe created MAPREDUCE-4818:

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

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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message