hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3937) Job history may get disabled due to overly long job names
Date Wed, 13 Aug 2008 17:14:44 GMT

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

Amar Kamat commented on HADOOP-3937:

I am planning to remove {{job-history-start-time}} from the job history filename as a part
of HADOOP-3245. Look [here|https://issues.apache.org/jira/browse/HADOOP-3245?focusedCommentId=12620042#action_12620042]
for more details. This was introduced by HADOOP-239 since the job names were not unique when
the patch was written. The reason why username and jobname are part of the history filename
is because JobHistoryViewer uses  history filename to find out the username and jobname. The
need is to detect the username and the jobname without reading the history file. We could
very well use the jobid as the history filename and maintain an _index_ file to map job-id
to _{username,jobname}_. 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.

View raw message