[
https://issues.apache.org/jira/browse/MAPREDUCE-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122357#comment-13122357
]
Eric Payne commented on MAPREDUCE-2783:
---------------------------------------
Fixed event handling within RMAppAttemptImpl to empty out the stale tracking
URL field so that the scheduler UI would not point to a stale link. No unit
test is feasable.
Manual tests were as follows:
1) Start task (wordcount) and kill -9 MRAppMaster. Result is that scheduler UI
shows 'UNASSIGNED' in 'Tracking UI' column. 'UNASSIGNED' is not a stale link.
2) Start task (wordcount) and kill using 'bin/mapred job kill'. Scheduler UI
shows 'History' in 'Tracking UI' column. 'History' is a link to the job history
page for the killed job.
> mr279 job history handling after killing application
> ----------------------------------------------------
>
> Key: MAPREDUCE-2783
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2783
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Thomas Graves
> Assignee: Eric Payne
> Priority: Critical
> Attachments: MAPREDUCE-2783.v1.txt
>
> Time Spent: 24h
>
> The job history/application tracking url handling during kill is not
> consistent. Currently if you kill a job that was running the tracking url
> points to job history, but job history server doesn't have the job.
--
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
