[jira] [Commented] (YARN-2000) Fix ordering of starting services inside the RM

2015-05-11 Thread Jian He (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)


[jira] [Commented] (YARN-2000) Fix ordering of starting services inside the RM

2014-06-13 Thread Jian He (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)


[jira] [Commented] (YARN-2000) Fix ordering of starting services inside the RM

2014-06-13 Thread Tsuyoshi OZAWA (JIRA)

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

Tsuyoshi OZAWA commented on YARN-2000:
--

It sounds reasonable to me.

 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)


[jira] [Commented] (YARN-2000) Fix ordering of starting services inside the RM

2014-05-02 Thread Tsuyoshi OZAWA (JIRA)

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

Tsuyoshi OZAWA commented on YARN-2000:
--

Hi [~jianhe], do you mind finishing YARN-1474? These JIRAs can be conflicted.

 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)


[jira] [Commented] (YARN-2000) Fix ordering of starting services inside the RM

2014-05-02 Thread Tsuyoshi OZAWA (JIRA)

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

Tsuyoshi OZAWA commented on YARN-2000:
--

typoed: s/do you mind finishing/do you mind if you wait for finishing/

 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)