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 "Lohit Vijayarenu (JIRA)" <ji...@apache.org> on 2013/01/22 23:04:12 UTC
[jira] [Resolved] (YARN-351) ResourceManager NPE during
allocateNodeLocal
[ https://issues.apache.org/jira/browse/YARN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lohit Vijayarenu resolved YARN-351.
-----------------------------------
Resolution: Duplicate
Thanks [~sandyr]. It does looks like it is solved in YARN-335. I was running one or two day's earlier build than your fix.
> ResourceManager NPE during allocateNodeLocal
> --------------------------------------------
>
> Key: YARN-351
> URL: https://issues.apache.org/jira/browse/YARN-351
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.2-alpha
> Reporter: Lohit Vijayarenu
> Priority: Critical
>
> ResourceManager seem to die due to NPE shown below on FairScheduler.
> This is easily reproduced on a cluster with multiple racks and nodes within each rack. Simple job with multiple tasks on each node triggers NPE in RM.
> Without understanding actual workings, I tried to do a null check which looked like it solved problem. But I am not sure if that is the right behavior yet.
> I feel this is serious enough to be marked as blocker, what do you guys think?
> {noformat}
> 2013-01-22 20:07:45,073 DEBUG org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo: allocate: applicationId=application_1358885180585_0001 container=container_1358885180585_0001_01_000830 host=x.x.x.x:36186
> 2013-01-22 20:07:45,074 FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in handling event type NODE_UPDATE to the scheduler
> java.lang.NullPointerException
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.allocateNodeLocal(AppSchedulingInfo.java:259)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AppSchedulingInfo.allocate(AppSchedulingInfo.java:220)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerApp.allocate(FSSchedulerApp.java:544)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable.assignContainer(AppSchedulable.java:250)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable.assignContainer(AppSchedulable.java:318)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSLeafQueue.assignContainer(FSLeafQueue.java:180)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.nodeUpdate(FairScheduler.java:796)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:859)
> at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:98)
> at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:375)
> at java.lang.Thread.run(Thread.java:662)
> 2013-01-22 20:07:45,075 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira