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 "Nigel Daley (JIRA)" <ji...@apache.org> on 2007/10/13 02:08:50 UTC
[jira] Updated: (HADOOP-2037) job_null_0001 in jobid
[ https://issues.apache.org/jira/browse/HADOOP-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-2037:
--------------------------------
Fix Version/s: 0.15.0
Assignee: Owen O'Malley
Priority: Blocker (was: Minor)
I'm marking this a blocker for 0.15. I think we should find out how this could occur as it may have other sinister effects on the system.
> job_null_0001 in jobid
> ----------------------
>
> Key: HADOOP-2037
> URL: https://issues.apache.org/jira/browse/HADOOP-2037
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.14.1
> Reporter: Koji Noguchi
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.15.0
>
>
> When I submit a job before jobtracker is fully up, I occasionally get jobid of job_null_0001.
> [knoguchi ]$ hadoop -jar ...
> 07/10/12 00:15:07 INFO mapred.FileInputFormat: Total input paths to process : 4
> 07/10/12 00:15:08 INFO mapred.JobClient: Running job: *job_null_0001*
> 07/10/12 00:15:09 INFO mapred.JobClient: map 0% reduce 0%
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.