[
https://issues.apache.org/jira/browse/HADOOP-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511253
]
Owen O'Malley commented on HADOOP-1473:
---------------------------------------
The Hadoop-QA failure seems to be streaming TestSymLinks, which is generally
flaky and not the fault of the patch. (Although I did have to change other
tests to work with the new job ids.)
Base-36 numbers are ugly and hard for users to remember and distinguish. I can
figure out yesterday's date in the readable form, but not in base-36. I think
it is a big usability hit to make the numbers unreadable. I often have people
tell me look at job 75 on node1000. That is much harder if it is some strange
combination of digits and numbers.
> 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.
