You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2014/06/13 21:25:02 UTC
[jira] [Commented] (YARN-2000) Fix ordering of starting services
inside the RM
[ https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031043#comment-14031043 ]
Jian He commented on YARN-2000:
-------------------------------
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.
> 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)