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 "Ramya R (JIRA)" <ji...@apache.org> on 2009/05/27 13:30:47 UTC

[jira] Commented: (HADOOP-5924) JT fails to recover the jobs after restart after HADOOP:4372

    [ https://issues.apache.org/jira/browse/HADOOP-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713538#action_12713538 ] 

Ramya R commented on HADOOP-5924:
---------------------------------

Submitted a job and restarted the JT after sometime. Below is the snapshot of the JT log:

{noformat}
INFO org.apache.hadoop.mapred.JobTracker: Submitting job <jobID> on behalf of user <user> in groups :<group>
INFO org.apache.hadoop.mapred.JobHistory: Recovered job history filename for job <jobID> is <job history file>
INFO org.apache.hadoop.mapred.JobHistory:  <job history file> exists!
INFO org.apache.hadoop.mapred.JobHistory: <job history file> exists!
INFO org.apache.hadoop.mapred.JobQueuesManager: Job submitted to queue default
WARN org.apache.hadoop.fs.FSInputChecker: Problem opening checksum file: file:<logs>history/<job history file>
Ignoring exception: java.io.EOFException
        at java.io.DataInputStream.readFully(DataInputStream.java:180)
        at java.io.DataInputStream.readFully(DataInputStream.java:152)
        at org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSInputChecker.<init>(ChecksumFileSystem.java:134)
        at org.apache.hadoop.fs.ChecksumFileSystem.open(ChecksumFileSystem.java:283)
        at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:351)
        at org.apache.hadoop.mapred.JobHistory.parseHistoryFromFS(JobHistory.java:254)
        at org.apache.hadoop.mapred.JobTracker$RecoveryManager.recover(JobTracker.java:1361)
        at org.apache.hadoop.mapred.JobTracker.offerService(JobTracker.java:1850)
        at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:3695)
INFO org.apache.hadoop.mapred.JobHistory: Deleting job history file <job history file>
INFO org.apache.hadoop.mapred.JobTracker: Restoration complete
INFO org.apache.hadoop.mapred.JobInitializationPoller: Passing to Initializer Job Id :<jobID> User:<user> Queue : default
INFO org.apache.hadoop.mapred.JobInitializationPoller: Initializing job : <jobID> in Queue default For user : <user>
INFO org.apache.hadoop.mapred.JobInProgress: Initializing <jobID>
INFO org.apache.hadoop.mapred.JobHistory: Nothing to recover for job <jobID>
INFO org.apache.hadoop.mapred.JobInitializationPoller: Job initialization failed:
java.lang.IllegalArgumentException: Can not create a Path from a null string
        at org.apache.hadoop.fs.Path.checkPathArg(Path.java:78)
        at org.apache.hadoop.fs.Path.<init>(Path.java:90)
        at org.apache.hadoop.fs.Path.<init>(Path.java:45)
        at org.apache.hadoop.mapred.JobHistory$JobInfo.getJobHistoryLogLocation(JobHistory.java:577)
        at org.apache.hadoop.mapred.JobHistory$JobInfo.logSubmitted(JobHistory.java:871)
        at org.apache.hadoop.mapred.JobInProgress.initTasks(JobInProgress.java:405)
        at org.apache.hadoop.mapred.JobInitializationPoller$JobInitializationThread.initializeJobs(JobInitializationPoller.java:143)
        at org.apache.hadoop.mapred.JobInitializationPoller$JobInitializationThread.run(JobInitializationPoller.java:113)
INFO org.apache.hadoop.mapred.JobHistory: Nothing to recover for job <jobID>
INFO org.apache.hadoop.mapred.JobInitializationPoller: Removing killed/completed job from initalized jobs list : <jobID>
{noformat}

The job fails to recover and is marked as failed. This happens for all the jobs(irrespective of map/reduce progress)


> JT fails to recover the jobs after restart after HADOOP:4372
> ------------------------------------------------------------
>
>                 Key: HADOOP-5924
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5924
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Ramya R
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.