You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Daniel Templeton (JIRA)" <ji...@apache.org> on 2017/11/08 17:23:01 UTC

[jira] [Commented] (YARN-7457) Delay scheduling should be an individual policy instead of part of scheduler implementation

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

Daniel Templeton commented on YARN-7457:
----------------------------------------

I think it makes good sense to abstract that out as a service.  It was actually on my todo list.

> 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: Wangda Tan
>
> 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.



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