[
https://issues.apache.org/jira/browse/HADOOP-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511278
]
Sameer Paranjpye commented on HADOOP-1473:
------------------------------------------
+1 for date/times, they're generally easier to remember than random strings.
Also, do we want the date/time of the jobtracker re-start to be in the job
name? Would it make sense to just re-cycle job id's every day?
When scanning for a job it would be easy to scan for 'job 4 from Wednesday the
11th', rather than 'job 4 after the restart on Wednesday the 11th'
> Make jobids unique across jobtracker restarts
> ---------------------------------------------
>
> Key: HADOOP-1473
> URL: https://issues.apache.org/jira/browse/HADOOP-1473
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.14.0
>
> Attachments: new-job-id.patch
>
>
> I'll make the job ids unique across JobTracker restarts by adding the startup
> time of the JobTracker, so if the JobTracker started at 8 Jun 2007 14:50, the
> first job would be called:
> job_200706081450_00001
> the second job would be:
> job_200706081450_00002
> and so on...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
