[
https://issues.apache.org/jira/browse/YARN-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291209#comment-16291209
]
Wangda Tan commented on YARN-7457:
----------------------------------
[~cheersyang], thanks for the comment. I also agree that putting it to
AMContainerSpec might be weird. However, it seems like the simplest way for
applications to consume. One idea from [~sunilg] is to introduce a String to
String map inside ApplicationSubmissionContext (or RegisterAMRequest) just for
scheduling hint, and it will copy AMSpec#environment if the scheduling hint map
is absent. Sounds like a plan?
Regarding this JIRA, I would suggest to split it into two parts, the first part
is to do refactorings to existing implementations and move logics from
scheduler to app placement allocator. 2nd part is to change APIs and allow apps
to choose delay scheduling policy.
> Delay scheduling should be an individual policy instead of part of scheduler
> implementation
> -------------------------------------------------------------------------------------------
>
> Key: YARN-7457
> URL: https://issues.apache.org/jira/browse/YARN-7457
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Tao Yang
>
> Currently, different schedulers have slightly different delay scheduling
> implementations. Ideally we should make delay scheduling independent from
> scheduler implementation. Benefits of doing this:
> 1) Applications can choose which delay scheduling policy to use, it could be
> time-based / missed-opportunistic-based or whatever new delay scheduling
> policy supported by the cluster. Now it is global config of scheduler.
> 2) Make scheduler implementations simpler and reusable.
> h2. {color:red}Running design doc:
> https://docs.google.com/document/d/1rY-CJPLbGk3Xj_8sxre61y2YkHJFK8oqKOshro1ZY3A/edit#heading=h.xnzvh9nn283a{color}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
