[ https://issues.apache.org/jira/browse/MAPREDUCE-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe resolved MAPREDUCE-3294. ----------------------------------- Resolution: Duplicate This was fixed by MAPREDUCE-5692. > Log the reason for killing a task during speculative execution > -------------------------------------------------------------- > > Key: MAPREDUCE-3294 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3294 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Ramya Sunil > > The reason for killing a speculated task has to be logged. Currently, a > speculated task is killed with a note of "Container killed by the > ApplicationMaster. Container killed on request. Exit code is 137" which is > not very useful. Better logging of this message stating the task was killed > due to completion of its speculative task would be useful. > Also, this message is lost once the app is moved to history. All we are left > with is a list of killed tasks without a reason being notified to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org