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

No process to track when operations are set to non-default priority

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      Internal operations can now opt for a non-default priority via their AdmissionContext.

      This ticket can serve as a placeholder for discussion:
      (1) Would it be useful to track all new commits which change an operations default priority?
      (2) What is the most practical approach?

      The solution could be a simple as "won't do", adding some sort of commit hook/ list which tracks server tickets make operations opt out of default priority, etc.

      A manual list could risk becoming stale quick, and as more operations utilize re-prioritisation, maybe we need a formal process.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: