Investigate components/operations owned by the storage execution team which may be affected by deprioritization

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • CAR Team 2026-02-16, Workload Resilience 2026-02-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In this ticket, we will reach out to the storage execution team to understand which components/operations they own which may be affected by deprioritization under the 3 yield heuristic which should not be deprioritized.

      We are already aware of the following potentially affected components:

      • Validation (confirmed non-issue)
      • Index builds
      • TTL deletions

      Follow up tickets will be created to investigate in depth each component/operation identified by this initial ticket.

      If an operation is brought up which would not be caught under the 3 yield heuristic but the team suspects it should be given the exempt status anyways (for example, operations under the critical section) please include this as well in the ticket response.

      Please use memento to capture any slack discussion in this ticket's comments rather than linking to the slack discussion so that we can keep the information all in this ticket.

            Assignee:
            Jiaqi Tian
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: