hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3937) Job history may get disabled due to overly long job names
Date Mon, 18 Aug 2008 20:43:44 GMT

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

Owen O'Malley commented on HADOOP-3937:
---------------------------------------

Until we have HADOOP-3245, it seems reasonable to put an upper limit on job names. I'm +1
on committing this one. 

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


Mime
View raw message