hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5641) Possible NPE in CapacityScheduler's MemoryMatcher
Date Tue, 12 May 2009 10:11:45 GMT

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

Hemanth Yamijala commented on HADOOP-5641:

Results of test-patch:

     [exec] +1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 3 new or modified tests.
     [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.
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.

As this patch touches only capacity scheduler tests, I ran all capacity scheduler tests and
all passed.

> Possible NPE in CapacityScheduler's MemoryMatcher
> -------------------------------------------------
>                 Key: HADOOP-5641
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5641
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Vinod K V
>            Assignee: rahul k singh
>         Attachments: HADOOP-5641.patch
> MemoryMatches does a job lookup based on a JobID in its getMemReservedForTasks(TaskTrackerStatus
taskTracker) method. By this time, job might have been removed from JT's memory resulting
in a NPE.

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

View raw message