[ 
https://issues.apache.org/jira/browse/YARN-7457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292621#comment-16292621
 ] 

Tao Yang commented on YARN-7457:
--------------------------------

Thanks all for your comments. 
I didn't clarify the true purpose about this work at first. Now from your 
discussions, now I have some questions:
* Overall, the purpose of this JIRA is to handle all delay scheduling 
requirements and the implementation can be splitted to two parts. 
The current part of this JIRA is to just concern about locality delay 
scheduling for legacy apps who use ResourceRequest and should not change APIs. 
The future part is to support DELAY_OR in PlacementConstraintExpression and the 
current work should consider common interface and procedure for it. Right?
* Regarding of ditching the missed opportunities option, it means that the 
delay scheduling definition from apps is time-based but default delay 
scheduling conf in scheduler is still missed-opportunistic-based (no need to 
change), right? 
* StringStringMap of scheduling hint in ApplicationSubmissionContext from 
YARN-7494 can't be found in the v1 patch, [~sunilg], will it be changed in v2 
patch?

> 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]

Reply via email to