[YARN-2671] ApplicationSubmissionContext change breaks the existing app submission

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: resourcemanager
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Zhijie Shen
• Created: 09/Oct/14 22:53
• Updated: 01/Dec/14 03:09
• Resolved: 10/Oct/14 01:02

Description

After YARN-2493, app submission goes wrong with the following exception:

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)

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.

Issue Links

• is broken by: YARN-2493 API changes for users