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 "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/05/12 12:09:45 UTC

[jira] Updated: (HADOOP-5641) Possible NPE in CapacityScheduler's MemoryMatcher

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

Hemanth Yamijala updated HADOOP-5641:
-------------------------------------

    Attachment: HADOOP-5641.patch

This patch fixes the NPE by implementing the proposal described in comments above. It checks for Null in the lookup for the job in MemoryMatcher, and returns nothing to the TT when such a state is determined. It also includes a test case for simulating this condition.

Both the unit test and manual tests were run with and without the patch to make sure the fix works.

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