You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2014/05/05 11:49:15 UTC
[jira] [Updated] (MAPREDUCE-5867) Possible NPE in
KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy
[ https://issues.apache.org/jira/browse/MAPREDUCE-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G updated MAPREDUCE-5867:
-------------------------------
Attachment: MapReduce-5867.3.patch
Yes Devaraj. I have added a test class for AMPreemptPolicy.
Please review the same.
> Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5867
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5867
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: MapReduce-5867.2.patch, MapReduce-5867.3.patch, Yarn-1980.1.patch
>
>
> I configured KillAMPreemptionPolicy for My Application Master and tried to check preemption of queues.
> In one scenario I have seen below NPE in my AM
> 014-04-24 15:11:08,860 ERROR [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: ERROR IN CONTACTING RM.
> java.lang.NullPointerException
> at org.apache.hadoop.mapreduce.v2.app.rm.preemption.KillAMPreemptionPolicy.preempt(KillAMPreemptionPolicy.java:57)
> at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.getResources(RMContainerAllocator.java:662)
> at org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator.heartbeat(RMContainerAllocator.java:246)
> at org.apache.hadoop.mapreduce.v2.app.rm.RMCommunicator$1.run(RMCommunicator.java:267)
> at java.lang.Thread.run(Thread.java:662)
> I was using 2.2.0 and merged MAPREDUCE-5189 to see how AM preemption works.
--
This message was sent by Atlassian JIRA
(v6.2#6252)