hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4209) The TaskAttemptID should not have the JobTracker start time
Date Tue, 23 Sep 2008 09:02:47 GMT

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

Enis Soztutar commented on HADOOP-4209:
---------------------------------------

Both of the proposals change the attemptid format, although the first one is implicit. But
I am not sure if we want to put 2 different integers in one field, instead of keeping them
separate. 
The format is very similar to the current one, except timestamp is an incrementing int, and
attempt id and timestamp places switched. 
The initial reason we have introduced job, task, attempt ids is that folks should not in any
case parse the strings, and we can make changes to the format w/o breaking compatibility.
However if you are concerned about compatibility then we should go with Owen's suggestion.


> 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