[MAPREDUCE-5317] Stale files left behind for failed jobs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.4-alpha, 0.23.8, 3.0.0-alpha1
• Fix Version/s: 0.23.10, 2.1.1-beta
• Component/s: mrv2
• Hadoop Flags: Reviewed
• Assignee: Ravi Prakash
• Reporter: Ravi Prakash
• Created: 10/Jun/13 22:54
• Updated: 12/May/16 18:22
• Resolved: 23/Jul/13 17:01

Description

Courtesy amar_kamat!

We are seeing _temporary files left behind in the output folder if the job
fails.
The job were failed due to hitting quota issue.
I simply ran the randomwriter (from hadoop examples) with the default setting.
That failed and left behind some stray files.

Issue Links

• breaks: MAPREDUCE-5888 Failed job leaves hung AM after it unregisters
• is related to: TEZ-263 Stale files left behind for failed jobs
• is related to: MAPREDUCE-5746 Job diagnostics can implicate wrong task for a failed job