[jira] [Assigned] (MAPREDUCE-3530) Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop

2011-12-13 Thread Arun C Murthy (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun C Murthy reassigned MAPREDUCE-3530:


Assignee: Arun C Murthy  (was: Vinod Kumar Vavilapalli)

I'll take a look.

 Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop
 ---

 Key: MAPREDUCE-3530
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3530
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: mrv2, resourcemanager, scheduler
Affects Versions: 0.23.1
Reporter: Karam Singh
Assignee: Arun C Murthy
Priority: Blocker

 Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop 
 but ResourceManager keeps on running.
 I have been observing intermitently for last 3 weeks.
 But with latest svn code. I tried to run sort twice and both times Job got 
 stuck due to NPE.
 {code}
 java.lang.NullPointerException
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApp.containerLaunchedOnNode(SchedulerApp.java:181)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.containerLaunchedOnNode(CapacityScheduler.java:596)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.nodeUpdate(CapacityScheduler.java:539)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:617)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:77)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:294)
 at java.lang.Thread.run(Thread.java:619)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (MAPREDUCE-3530) Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop

2011-12-12 Thread Arun C Murthy (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun C Murthy reassigned MAPREDUCE-3530:


Assignee: Vinod Kumar Vavilapalli

 Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop
 ---

 Key: MAPREDUCE-3530
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3530
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: mrv2, resourcemanager, scheduler
Affects Versions: 0.23.1
Reporter: Karam Singh
Assignee: Vinod Kumar Vavilapalli
Priority: Blocker

 Sometimes NODE_UPDATE to the scheduler throws NPE causes scheduling to stop 
 but ResourceManager keeps on running.
 I have been observing intermitently for last 3 weeks.
 But with latest svn code. I tried to run sort twice and both times Job got 
 stuck due to NPE.
 {code}
 java.lang.NullPointerException
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApp.containerLaunchedOnNode(SchedulerApp.java:181)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.containerLaunchedOnNode(CapacityScheduler.java:596)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.nodeUpdate(CapacityScheduler.java:539)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:617)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:77)
 at 
 org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:294)
 at java.lang.Thread.run(Thread.java:619)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira