- 
    Type:Task 
- 
    Resolution: Unresolved
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: None
- 
    None
- 
        Cluster Scalability
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
This comment outlines cases where CancellationSource is used in Cluster Scalability owned operations. In resharding, this seems to have been implicated in growing memory usage (see SERVER-112696).
SERVER-113039 was filed to address this in resharding. This ticket should serve to track all similar efforts in other operations owned by Cluster Scalability.
- depends on
- 
                    SERVER-113039 Stop attaching to the root cancelToken in resharding -         
- Needs Scheduling
 
-         
- is related to
- 
                    SERVER-112089 Audit use of long lived CancellationSources in Cluster Scalability code -         
- Closed
 
-         
- 
                    SERVER-112696 Determine best practices with tcmalloc-google -         
- Closed
 
-