Karthik Kambatla commented on YARN-1474:

Sorry for the prolonging this discussion. If we don't change the 
{{reinitialize}} signature, we might not need setRMContext at all. Each 
scheduler can (re)set the local {{RMContext}}, may be we can start with setting 
it only on null. None of the tests need to change, I think the patch would be 
fairly small. 

Let us open another JIRA to revisit the ResourceScheduler API, and may be we 
can add the new setRMContext and update reinitialize? What do you think? 

> Make schedulers services
> ------------------------
>                 Key: YARN-1474
>                 URL: https://issues.apache.org/jira/browse/YARN-1474
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.3.0, 2.4.0
>            Reporter: Sandy Ryza
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-1474.1.patch, YARN-1474.10.patch, 
> YARN-1474.11.patch, YARN-1474.12.patch, YARN-1474.13.patch, 
> YARN-1474.14.patch, YARN-1474.2.patch, YARN-1474.3.patch, YARN-1474.4.patch, 
> YARN-1474.5.patch, YARN-1474.6.patch, YARN-1474.7.patch, YARN-1474.8.patch, 
> YARN-1474.9.patch
> Schedulers currently have a reinitialize but no start and stop.  Fitting them 
> into the YARN service model would make things more coherent.

This message was sent by Atlassian JIRA

Reply via email to