[ 
https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538822#comment-14538822
 ] 

Jian He commented on YARN-2000:
-------------------------------

bq. Probably we can have state-store stop last so that all the other services 
are stopped first and won't accept more requests and send events to state-store.
Even if state-store stops first, the API calls such as submitApplication won't 
return true until the state-store operation completes. 
Nothing to be done, close.

> 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.3.4#6332)

Reply via email to