hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7457) Delay scheduling should be an individual policy instead of part of scheduler implementation
Date Mon, 18 Dec 2017 11:28:00 GMT

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

Sunil G commented on YARN-7457:
-------------------------------

Thank you. I raised YARN-7666 to track this.

> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message