[ https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik Kambatla updated YARN-2000: ----------------------------------- Target Version/s: 2.6.0 (was: 2.5.0) > Fix ordering of starting services inside the RM > ----------------------------------------------- > > Key: YARN-2000 > URL: https://issues.apache.org/jira/browse/YARN-2000 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Jian He > Assignee: Jian He > > 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. -- This message was sent by Atlassian JIRA (v6.2#6252)