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

Separate TicketHolder management from TicketHolder logic

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Execution Team 2022-10-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Description
      Right now, the ReaderWriterTicketHolder conflates the concept of managing a pool of tickets versus multiple pools of tickets. The ReaderWriterTicketHolder could be removed to separate the TicketHolder management (management of multiple pools of tickets) from the TicketHolder class (distribution of a single pool of tickets)

      Original Description
      (work for this ticket has been moved to SERVER-70792)

      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:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: