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 Fri, 19 Sep 2008 14:16:44 GMT

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

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

How about 
{code}
attempt_200707121733_0003_m_000005_0_0
attempt_200707121733_0003_m_000005_0_1 // fails once
attempt_200707121733_0003_m_000005_1_0 // after a restart
attempt_200707121733_0003_m_000005_1_1 // fails after restart
attempt_200707121733_0003_m_000005_2_0 // after a second restart
{code}
The attempt count and history count need not be merged into one like "1001". Keeping them
separate would simplify the code. 

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