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 2009/04/03 17:24:14 UTC
[jira] Commented: (HADOOP-5149) HistoryViewer throws
IndexOutOfBoundsException when there are files or directories not confrming
to log file name convention
[ https://issues.apache.org/jira/browse/HADOOP-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695443#action_12695443 ]
Hudson commented on HADOOP-5149:
--------------------------------
Integrated in Hadoop-trunk #796 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/796/])
> HistoryViewer throws IndexOutOfBoundsException when there are files or directories not confrming to log file name convention
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5149
> URL: https://issues.apache.org/jira/browse/HADOOP-5149
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.21.0
> Reporter: Hong Tang
> Assignee: Hong Tang
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HADOOP-5149.trunk.patch
>
>
> When running history viewer in local mode (specifying file:///<path/to/hodlogs> as path to logs), it throws IndexOutOfBoundsException due to the following code:
> {code}
> String[] jobDetails =
> JobInfo.decodeJobHistoryFileName(jobFiles[0].getName()).split("_");
> trackerHostName = jobDetails[0];
> trackerStartTime = jobDetails[1];
> {code}
> The reason is because there are some directories under the log directories that do not conform to the log file naming convention, and the length of the jobDetails array is 1.
> History viewer should be more defensive and ignore (possibly with warning) files or directories that it does not recognize.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.