Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <62510988.1221514904384.JavaMail.jira@brutus>
Date: Mon, 15 Sep 2008 14:41:44 -0700 (PDT)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4112) Got ArrayOutOfBound exception while
 analyzing the job history
In-Reply-To: <585453316.1220851244395.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on HADOOP-4112:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12389987/patch-4112.txt
  against trunk revision 695604.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3262/console

This message is automatically generated.

> 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
>    Affects Versions: 0.19.0
>            Reporter: Amar Kamat
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.19.0
>
>         Attachments: patch-4112.txt, patch-4112.txt, patch-4112.txt, 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.