[jira] Updated: (HADOOP-4112) Got ArrayOutOfBound exception while analyzing the job history

["Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated HADOOP-4112:
--------------------------------------------

    Attachment: patch-4112.txt

Here is patch doing the following:
1. Adds CleanupAttempt to JobHistory. The cleanup tasks are logged in history as CleanupAttempts. And the TASK_TYPE is CLEANUP.  This change also fixes ArrayOutOfBoundException in analyzeJob link.
2. Updates JobTasksParseListener about CleanupAttempt
3. JobInProgress is modified to log the cleanup task as CleanupAttempt. Also removes an extra JobFailed log from history.
4. Updates jobhistory.jsp and HistoryViewer.java to show cleanup task.



> Got ArrayOutOfBound exception while analyzing the job history
> -------------------------------------------------------------
>
>                 Key: HADOOP-4112
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4112
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amareshwari Sriramadasu
>         Attachments: patch-4112.txt
>
>
> HADOOP-3150 introduced 2 new type of tasks called the cleanup tasks. These are logged to history either as map tasks or reduce tasks. The number of maps/reducers is also logged to history. Since the number of maps will be less than the total number of map tasks logged to history (actual num maps + cleanup tasks), I think thats the reason for this exception. The important question is to investigate the effect of HADOOP-3150 on job history and code related to it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.