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-4209) The TaskAttemptID should not have the JobTracker start time
Date Mon, 06 Oct 2008 05:51:44 GMT

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

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

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Amar!

I don't think this should be an incompatible change, because relative to 0.18, all that changed
was that the task attempt ids are formatted to always have 4 digits.

> The TaskAttemptID should not have the JobTracker start time
> -----------------------------------------------------------
>
>                 Key: HADOOP-4209
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4209
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-4209-v1.1.patch, HADOOP-4209-v1.2.patch, HADOOP-4209-v1.patch
>
>
> The TaskAttemptID now includes the redundant copy of the JobTracker's start time as milliseconds.
We should instead change the JobID to have the longer unique string.

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