[
https://issues.apache.org/jira/browse/HADOOP-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622249#action_12622249
]
Matei Zaharia commented on HADOOP-3937:
---------------------------------------
Isn't the combination of start time and job ID enough? Job ID's are already
unique within a JobTracker. The start time also includes the name of the
machine the JobTracker ran on. Therefore the only way you could have a conflict
is if you start a JobTracker twice in the same millisecond on the same machine
and actually run jobs on both of the instances, which should be impossible.
Before Hadoop 0.17, I think we only used <i>job-history-start-time_job-id</i>
and this worked fine (the job name and username were added so as not to have to
create an index file).
> Job history may get disabled due to overly long job names
> ---------------------------------------------------------
>
> Key: HADOOP-3937
> URL: https://issues.apache.org/jira/browse/HADOOP-3937
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.17.0, 0.17.1, 0.18.0, 0.19.0
> Reporter: Matei Zaharia
> Attachments: HADOOP-3937.patch
>
>
> Since Hadoop 0.17, the job history logs include the job's name in the
> filename. However, this can lead to overly long filenames, because job names
> may be arbitrarily long. When a filename is too long for the underlying OS,
> file creation fails and the JobHistory class silently disables history from
> that point on. This can lead to days of lost history until somebody notices
> the error in the log.
> Proposed solution: Trim the job name to a reasonable length when selecting a
> filename for the history file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
