hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance Riedel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5761) JobTracker and TaskTracker enter infinite loop when TaskTracker reports bad taskid
Date Thu, 14 May 2009 20:51:45 GMT

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

Lance Riedel commented on HADOOP-5761:
--------------------------------------

This is very high priority for us as we have a very unstable production cluster (dying with
this issue every day or so). 

> JobTracker and TaskTracker enter infinite loop when TaskTracker reports bad taskid
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-5761
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5761
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Todd Lipcon
>
> If the TaskTracker somehow gets into a state where it has a task in COMMIT_PENDING state
that the JobTracker does not know about, the JobTracker will throw NPEs while processing heartbeats.
Due to HADOOP-3987, this causes the JT and TT to enter an infinite heartbeat loop with no
delays, and the TT fails to make progress.

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