Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70792

Separate scheduling policy from ticketholder implementation

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2023-01-23

      The PriorityTicketHolder is currently a quite coupled pairing of implementation and scheduling policy. We want to move to a world where we can test different policies with ease.

      This should help improve testing and reasoning of the policy behaviour.

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: