[
https://issues.apache.org/jira/browse/HADOOP-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634776#action_12634776
]
Owen O'Malley commented on HADOOP-4209:
---------------------------------------
Let's go with the 1000*reboots + attempt. I think it will create less user
confusion, since most jobs will have it set to 0. If we add the new number and
it is always 0, users will be confused.
> 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.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.
