Mark the sessions collection reap and refresh as non-deprioritizable

XMLWordPrintableJSON

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

      These operations free up in memory resources (active sessions and session catalog) and so deferring them can cause increased memory usage. Additionally, failing to refresh the sessions collection can cause the in memory sessions cache to fill up to the point that there are no free sessions available, and this can cause write unavailability. We should mark both of these jobs as non-deprioritizable.

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

              Created:
              Updated: