Sarjeet Singh created MYRIAD-156:
------------------------------------

             Summary: NullPointerException from "Error in handling event type 
NODE_RESOURCE_UPDATE to the scheduler"
                 Key: MYRIAD-156
                 URL: https://issues.apache.org/jira/browse/MYRIAD-156
             Project: Myriad
          Issue Type: Bug
            Reporter: Sarjeet Singh


The NPE happens where there is a node in cluster becomes unhealthy, and 
scheduler removes them from internal data structure. However, when the node 
heartbeats and scheduler tries to search for this node, and try to operate on 
it, it gets nullPointerException there. Here is the code snippet where this is 
causing NPE: 

SchedulerNode node = getSchedulerNode(nm.getNodeID());
the node object is Null causing the Null pointer exception.

Here is the RM log for caused exception:

15/10/06 09:18:09 INFO handlers.ResourceOffersEventHandler: Offer not
sufficient for task with, cpu: 4.4, memory: 5504.0, spindles: 4.0, ports: 996
15/10/06 09:18:11 FATAL resourcemanager.ResourceManager: Error in handling
event type NODE_RESOURCE_UPDATE to the scheduler
java.lang.NullPointerException
    at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.updateNodeResource(AbstractYarnScheduler.java:548)
    at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.updateNodeResource(FairScheduler.java:1712)
    at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1293)
    at
com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:64)
    at
com.ebay.myriad.scheduler.yarn.MyriadFairScheduler.handle(MyriadFairScheduler.java:17)
    at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:693)
    at java.lang.Thread.run(Thread.java:745)
15/10/06 09:18:11 INFO resourcemanager.ResourceManager: Exiting, bbye..



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to