[ 
https://issues.apache.org/jira/browse/YARN-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524014#comment-14524014
 ] 

Jian He commented on YARN-1663:
-------------------------------

Give scheduler code has evolved so much, it's now not able to locate the 
correct line number with the stack trace.
It looks to be similar to YARN-1572, close as a dup.

> NPE in FifoScheduler.assignContainers
> -------------------------------------
>
>                 Key: YARN-1663
>                 URL: https://issues.apache.org/jira/browse/YARN-1663
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.3.0
>         Environment: (starting AM client that is marked as wanting containers 
> back on restart)
>            Reporter: Steve Loughran
>            Priority: Minor
>
> NPE see in scheduler thread running in a MiniYARNCluster with the fifo 
> scheduler
> {code}
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.assignContainers(FifoScheduler.java:461)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.nodeUpdate(FifoScheduler.java:718)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.handle(FifoScheduler.java:747)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.handle(FifoScheduler.java:105)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:543)
> {code}



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

Reply via email to