[
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]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[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.
