Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-5139 [Umbrella] Move YARN scheduler towards global scheduler
  3. YARN-7457

Delay scheduling should be an individual policy instead of part of scheduler implementation

Add voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Tao Yang Tao Yang
            leftnoteasy Wangda Tan

            Dates

              Created:
              Updated:

              Slack

                Issue deployment