hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-5272) JobTracker does not log TIP start information after restart
Date Tue, 24 Feb 2009 05:28:01 GMT

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

Devaraj Das resolved HADOOP-5272.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
                   0.20.0
         Assignee: Amar Kamat
     Hadoop Flags: [Reviewed]

I just committed this. Thanks, Amar!

> JobTracker does not log TIP start information after restart
> -----------------------------------------------------------
>
>                 Key: HADOOP-5272
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5272
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Critical
>             Fix For: 0.20.0, 0.21.0
>
>         Attachments: HADOOP-5272-v1.0.patch
>
>
> In case of JobTracker restart, attempt_0123456789_0001_m_000000_0 might not be the first
attempt to get scheduled as the attempt id offset changes after every restart. For example,

> upon first restart the new attempt id will be attempt_0123456789_0001_m_000000_1000.
Hence TIP start line never gets logged to the job history after the restart, TaskInProgress.isFirstAttempt()
always returns *false*.

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