Re-evaluate background operations prioritization

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-03-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-119153 we need to re-evaluate the way background operations like range deletions, TTL indexes and index builds are currently being de-prioritized. For example, range deletions only use the same operation context for all the range removals. With the new prioritization, considering the range deletion is marked to have a low priority, the number of admisisons in that context will grow, making the range deletion a very low priority operation. We could for example, create a new operation context for every range removal, or for every batch removal. The purpose of this ticket is to evaluate the resolution level of the operation context on each background operation, and ensure that the operation is still correct.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: