You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/02/22 21:44:39 UTC

[jira] Updated: (HADOOP-32) Creating job with InputDir set to non-existant directory locks up jobtracker

     [ http://issues.apache.org/jira/browse/HADOOP-32?page=all ]

Doug Cutting updated HADOOP-32:
-------------------------------

    Component: mapred

> 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
>         Type: Bug
>   Components: mapred
>  Environment: hadoop-trunk, running distributed map reduce
>     Reporter: Bryan Pendleton

>
> 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