Zhijie Shen created YARN-2671:
---------------------------------

             Summary: ApplicationSubmissionContext change breaks the existing 
app submission
                 Key: YARN-2671
                 URL: https://issues.apache.org/jira/browse/YARN-2671
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
            Reporter: Zhijie Shen


After YARN-2493, app submission goes wrong with the following exception:
{code}
2014-10-09 15:50:35,774 WARN  [297524352@qtp-1314143300-2 - 
/ws/v1/cluster/apps] webapp.GenericExceptionHandler 
(GenericExceptionHandler.java:toResponse(98)) - INTERNAL_SERVER_ERROR
java.lang.NullPointerException
        at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.validateResourceRequest(SchedulerUtils.java:194)
        at 
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.validateResourceRequest(RMAppManager.java:390)
        at 
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.createAndPopulateNewRMApp(RMAppManager.java:346)
        at 
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.submitApplication(RMAppManager.java:273)
        at 
org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.submitApplication(ClientRMService.java:570)
        at 
org.apache.hadoop.yarn.server.resourcemanager.webapp.RMWebServices$2.run(RMWebServices.java:896)
        at 
org.apache.hadoop.yarn.server.resourcemanager.webapp.RMWebServices$2.run(RMWebServices.java:1)
{code}

This is because resource is putting into ResourceRequest of 
ApplicationSubmissionContext, but not directly into 
ApplicationSubmissionContext, therefore the sanity check won't get resource 
object from context.



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

Reply via email to