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
Fix For: 0.23.0
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
