[ https://issues.apache.org/jira/browse/MAPREDUCE-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108266#comment-14108266 ]
Chen He commented on MAPREDUCE-4818: ------------------------------------ Does the "yarn-localization-log" introduces extra overhead to system (memory, disks, etc)? I mean there thousands of containers localizing data in a large busy cluster. How about we only record those failed ones. > 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 > Labels: usability > > 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.2#6252)