[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsuyoshi OZAWA updated YARN-1474:
---------------------------------
Attachment: YARN-1474.18.patch
Thanks for sharing the opinions, Sandy and Karthik. I also think it's OK to change internal
APIs' semantics because its interface is Evolving one. [~vinodkv], please let us know if you
have additional comments.
Updated patch with following changes to address Karthik's comments:
1. Removed {{initialized}} flag from *Schedulers. All initialization is done in {{serviceInit}}
and {{serviceStart}}, instead of {{reinitialize()}}.
2. Changed ResourceSchedulerWrapper to override {{serviceInit}}, {{serviceStart}}, {{serviceStop}}.
3. Updated some tests to call scheduler.init() right after scheduler.setRMContext() without
ResourceManager/MockRM.
> 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.15.patch, YARN-1474.16.patch, YARN-1474.17.patch,
YARN-1474.18.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
(v6.2#6252)
|