hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4209) The TaskAttemptID should not have the JobTracker start time
Date Fri, 19 Sep 2008 14:32:44 GMT

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

Amar Kamat updated HADOOP-4209:
-------------------------------

    Attachment: HADOOP-4209-v1.patch

Attaching a very basic patch. Changes are as follows 
1) Reverts the changes made to {{TaskAttememptID}} and changes related to it.
2) Adds the restart count to the history
3) Uses restart count while assigning ids to task attempts. This patch allows 1000 attempts
per task per restart.

Ant tests pass on my box. Testing on a cluster.

> 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
>            Reporter: Owen O'Malley
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: 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