[
https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011331#comment-14011331
]
Karthik Kambatla commented on YARN-1474:
----------------------------------------
I think that is the step in the right direction. I agree it is a change in
semantics. Might be a good idea to see what others think.
[~sandyr], [~vinodkv] - do you guys think it is okay to change the semantics on
how a scheduler is used:
- Before this patch, we create a scheduler and call reinitialize().
- After this patch, I am proposing scheduler.setRMContext(), scheduler.init(),
and then scheduler.reinitialize() for later updates to allocation-files etc.
Scheduler initialization is within the RM, and we haven't exposed the scheduler
API for users to write custom schedulers yet.
> 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.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)
