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

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Tao Yang
• Reporter: Wangda Tan
• Created: 08/Nov/17 00:14
• Updated: 18/Dec/17 11:27

Description

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.

Running design doc: https://docs.google.com/document/d/1rY-CJPLbGk3Xj_8sxre61y2YkHJFK8oqKOshro1ZY3A/edit#heading=h.xnzvh9nn283a