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 "Karam Singh (JIRA)" <ji...@apache.org> on 2009/02/25 12:34:01 UTC
[jira] Created: (HADOOP-5325) Jobs are getting stuck on
JobTracker restart
Jobs are getting stuck on JobTracker restart
-----------------------------------------------
Key: HADOOP-5325
URL: https://issues.apache.org/jira/browse/HADOOP-5325
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.20.0
Reporter: Karam Singh
Priority: Blocker
Recovery manager failed to recover the job properly and threw "
2009-02-25 09:24:09,944 INFO org.apache.hadoop.fs.FSInputChecker: Found checksum error: b[7168, 7168]=
org.apache.hadoop.fs.ChecksumException: Checksum error: file filename ".
. As part of recovery, one of the attempts got added to the expiry launching tasks list. But. another attempt of the same tip was relaunched with the same attempt id and the job was stuck. Looks like the attempt which got expired was marked as failed and newly launched attempt (with same attempt id) was successful and Jobtracker tried marking a failed tip as successful hence the tip was considered as failed but tip.isComplete returns true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5325) Jobs are getting stuck on
JobTracker restart
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-5325:
-------------------------------------
Fix Version/s: 0.20.0
> Jobs are getting stuck on JobTracker restart
> -----------------------------------------------
>
> Key: HADOOP-5325
> URL: https://issues.apache.org/jira/browse/HADOOP-5325
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
>
> Recovery manager failed to recover the job properly and threw "
> 2009-02-25 09:24:09,944 INFO org.apache.hadoop.fs.FSInputChecker: Found checksum error: b[7168, 7168]=
> org.apache.hadoop.fs.ChecksumException: Checksum error: file filename ".
> . As part of recovery, one of the attempts got added to the expiry launching tasks list. But. another attempt of the same tip was relaunched with the same attempt id and the job was stuck. Looks like the attempt which got expired was marked as failed and newly launched attempt (with same attempt id) was successful and Jobtracker tried marking a failed tip as successful hence the tip was considered as failed but tip.isComplete returns true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-5325) Jobs are getting stuck on
JobTracker restart
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat resolved HADOOP-5325.
--------------------------------
Resolution: Duplicate
HADOOP-4638 will take care of this.
> Jobs are getting stuck on JobTracker restart
> -----------------------------------------------
>
> Key: HADOOP-5325
> URL: https://issues.apache.org/jira/browse/HADOOP-5325
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
>
> Recovery manager failed to recover the job properly and threw "
> 2009-02-25 09:24:09,944 INFO org.apache.hadoop.fs.FSInputChecker: Found checksum error: b[7168, 7168]=
> org.apache.hadoop.fs.ChecksumException: Checksum error: file filename ".
> . As part of recovery, one of the attempts got added to the expiry launching tasks list. But. another attempt of the same tip was relaunched with the same attempt id and the job was stuck. Looks like the attempt which got expired was marked as failed and newly launched attempt (with same attempt id) was successful and Jobtracker tried marking a failed tip as successful hence the tip was considered as failed but tip.isComplete returns true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-5325) Jobs are getting stuck on
JobTracker restart
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat reassigned HADOOP-5325:
----------------------------------
Assignee: Amar Kamat
> Jobs are getting stuck on JobTracker restart
> -----------------------------------------------
>
> Key: HADOOP-5325
> URL: https://issues.apache.org/jira/browse/HADOOP-5325
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: Amar Kamat
> Priority: Blocker
>
> Recovery manager failed to recover the job properly and threw "
> 2009-02-25 09:24:09,944 INFO org.apache.hadoop.fs.FSInputChecker: Found checksum error: b[7168, 7168]=
> org.apache.hadoop.fs.ChecksumException: Checksum error: file filename ".
> . As part of recovery, one of the attempts got added to the expiry launching tasks list. But. another attempt of the same tip was relaunched with the same attempt id and the job was stuck. Looks like the attempt which got expired was marked as failed and newly launched attempt (with same attempt id) was successful and Jobtracker tried marking a failed tip as successful hence the tip was considered as failed but tip.isComplete returns true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.