[MAPREDUCE-5581] killing jobs which have failed causes log missing

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.1.1-beta
• Component/s: client
• Target Version/s: 2.1.1-beta
• Assignee: Unassigned
• Reporter: Nemon Lou
• Created: 12/Oct/13 08:19
• Updated: 14/Oct/13 14:05
• Resolved: 14/Oct/13 14:05

Description

In hive code,when a job failed,they invoke the RunningJob.killJob() API immediately.
From mapreduce client side,when job is at failed state,the YARNRunner will invoke resMgrDelegate.killApplication to kill that job.And this prevent AM from writing logs to job history server.

Issue Links

• duplicates: MAPREDUCE-5502 History link in resource manager is broken for KILLED jobs
• is broken by: MAPREDUCE-3054 Unable to kill submitted jobs