[ http://issues.apache.org/jira/browse/HADOOP-32?page=all ]
Owen O'Malley resolved HADOOP-32.
---------------------------------
Fix Version/s: 0.4.0
Resolution: Duplicate
Assignee: Owen O'Malley
This was fixed by 0.4.0 by the fix for HADOOP-278.
> Creating job with InputDir set to non-existant directory locks up jobtracker
> ----------------------------------------------------------------------------
>
> Key: HADOOP-32
> URL: http://issues.apache.org/jira/browse/HADOOP-32
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Environment: hadoop-trunk, running distributed map reduce
> Reporter: Bryan Pendleton
> Assigned To: Owen O'Malley
> Fix For: 0.4.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
