You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/09/19 06:12:44 UTC
[jira] Commented: (HADOOP-4209) The TaskAttemptID should not have
the JobTracker start time
[ https://issues.apache.org/jira/browse/HADOOP-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632504#action_12632504 ]
Owen O'Malley commented on HADOOP-4209:
---------------------------------------
I would propose that we should extend the jobid by HHMM, which will make all job ids where the JobTracker stays up more than a minute unique. I hope that is enough and that we don't really expect our JobTracker to only last 30 seconds and to launch jobs in that time. *grin*
> 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
> 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.