[HADOOP-32] Creating job with InputDir set to non-existant directory locks up jobtracker

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.4.0

Environment

hadoop-trunk, running distributed map reduce

• Assignee: Owen O'Malley
• Reporter: Bryan Pendleton
• Created: 10/Feb/06 16:07
• Updated: 08/Jul/09 16:51
• Resolved: 27/Jul/06 03:13

Description

This, in the very least, affects anything using the default listFiles() from InputFormatBase. If no files are enumerated, an exception is thrown... but the JobTracker keeps attempting to run listFiles() for this job. Trying to stop the job with hadoop job -kill job_name just results in timeouts, and further started jobs also don't progress. This happens every single time with, say, "wordcount", and a non-existent input path.