[jira] Commented: (HADOOP-3937) Job history may get disabled due to overly long job names

["Amar Kamat (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622248#action_12622248 ] 

Amar Kamat commented on HADOOP-3937:
------------------------------------

The current strategy for naming a history file is as follows
_job-history-start-time___job-id___job-name___user-name_. 
The reason for using this technique is to make sure that the job history filename remains unique across jobtrackers and across restarts. Making it 50 characters might cause the filenames to clash. We should probably come up with a strategy of giving shorter unique filenames to the job history. Thoughts?

> 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.