[YARN-2000] Fix ordering of starting services inside the RM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Component/s: resourcemanager
• Target Version/s: 2.6.0
• Assignee: Jian He
• Reporter: Jian He
• Created: 30/Apr/14 04:02
• Updated: 11/May/15 22:54
• Resolved: 11/May/15 22:54

Description

The order of starting services in RM would be:

• Recovery of the app/attempts
• Start the scheduler and add scheduler app/attempts
• Start ResourceTrackerService and re-populate the containers in scheduler based on the containers info from NMs
• ApplicationMasterService either don’t start or start but block until all the previous NMs registers.

Other than these, there are other services like ClientRMService, Webapps which we need to think about the order too.