hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4112) Got ArrayOutOfBound exception while analyzing the job history
Date Wed, 10 Sep 2008 05:47:44 GMT

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

Amareshwari Sriramadasu commented on HADOOP-4112:

test-patch result on the trunk:
     [exec] -1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified
     [exec]                         Please justify why no tests are needed for this patch.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.

All unit tests except TestHighRAMJobs passed on my machine.  TestHighRAMJobs failure is due
to HADOOP-4129

> 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
> 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.

View raw message