hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2037) job_null_0001 in jobid
Date Tue, 16 Oct 2007 19:53:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Owen O'Malley updated HADOOP-2037:
----------------------------------

    Fix Version/s:     (was: 0.15.0)
                   0.16.0
         Priority: Critical  (was: Blocker)

I'm downgrading this bug and moving it to 16 because it looks to be a race condition between
submitting a job and bringing up the cluster.

> 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: Critical
>             Fix For: 0.16.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.


Mime
View raw message