hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matei Zaharia (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-3937) Job history may get disabled due to overly long job names
Date Tue, 12 Aug 2008 18:47:44 GMT
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.1, 0.17.0, 0.18.0, 0.19.0
            Reporter: Matei Zaharia


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