You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2014/04/24 14:47:16 UTC
[jira] [Created] (YARN-1980) Possible NPE in KillAMPreemptionPolicy
related to ProportionalCapacityPreemptionPolicy
Sunil G created YARN-1980:
-----------------------------
Summary: Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy
Key: YARN-1980
URL: https://issues.apache.org/jira/browse/YARN-1980
Project: Hadoop YARN
Issue Type: Bug
Components: resourcemanager
Affects Versions: 2.3.0
Reporter: Sunil G
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)