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 "Hudson (JIRA)" <ji...@apache.org> on 2008/09/01 17:46:45 UTC
[jira] Commented: (HADOOP-3937) Job history may get disabled due to
overly long job names
[ https://issues.apache.org/jira/browse/HADOOP-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627492#action_12627492 ]
Hudson commented on HADOOP-3937:
--------------------------------
Integrated in Hadoop-trunk #589 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/589/])
> 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
> Assignee: Matei Zaharia
> Fix For: 0.19.0
>
> 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.