[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506992#comment-14506992 ]
gu-chi commented on YARN-2308: ------------------------------ Hi, Chang Li, as I went through the patches that you attached, previously these was + if (application==null) { + LOG.info("can't retireve application attempt"); + return; + } but, finally, the patch merged does not have this modification. Is this updated on purpose? What is the concern? I am now facing one scenario, App status is Finished and AppAttempt status is null, this way when doing recover, application is null in CS and then NPE occur. I am thinking if condition "application==null" was there, the issue I meet will not occur. > NPE happened when RM restart after CapacityScheduler queue configuration > changed > --------------------------------------------------------------------------------- > > Key: YARN-2308 > URL: https://issues.apache.org/jira/browse/YARN-2308 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, scheduler > Affects Versions: 2.6.0 > Reporter: Wangda Tan > Assignee: Chang Li > Priority: Critical > Fix For: 2.6.0 > > Attachments: YARN-2308.0.patch, YARN-2308.1.patch, jira2308.patch, > jira2308.patch, jira2308.patch > > > I encountered a NPE when RM restart > {code} > 2014-07-16 07:22:46,957 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in > handling event type APP_ATTEMPT_ADDED to the scheduler > java.lang.NullPointerException > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:566) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:922) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:98) > at > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:594) > at > org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46) > at > org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:654) > at > org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:85) > at > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:698) > at > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:682) > at > org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173) > at > org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106) > at java.lang.Thread.run(Thread.java:744) > {code} > And RM will be failed to restart. > This is caused by queue configuration changed, I removed some queues and > added new queues. So when RM restarts, it tries to recover history > applications, and when any of queues of these applications removed, NPE will > be raised. -- This message was sent by Atlassian JIRA (v6.3.4#6332)