Audit use of long lived CancellationSources in Cluster Scalability code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability Priorities
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Splitting this ticket from SERVER-92333 for each team. Copying the description over:

      Scheduling tasks on a cancellation token will keep those tasks alive in-memory until the token's underlying CancellationSource is destructed. If a cancellation source stays alive for a long time and has many tasks scheduled on it, this can lead to significant memory use, as in SERVER-92236. We should audit our use of cancellation sources for any that can live for a long time and probably rewrite them to at least periodically be cleared.

            Assignee:
            Brett Nawrocki
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: