- 
    Type:
Bug
 - 
    Resolution: Won't Fix
 - 
    Priority:
Major - P3
 - 
    None
 - 
    Affects Version/s: None
 - 
    Component/s: None
 
- 
        ALL
 - 
        v4.4
 - 
        Service arch 2020-04-20, Service arch 2020-05-04, Service arch 2020-05-18, Service arch 2020-06-29, Service arch 2020-07-13, Service Arch 2020-08-24, Service Arch 2021-06-28, Service Arch 2021-07-12, Service Arch 2021-08-09, Service Arch 2021-08-23, Service Arch 2021-09-06
 - 
        0
 - 
        1
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
When we issue a _killoperation to cancel a hedged read, we do not know if the remote server has already processed the original read and registered its clientOperationKey. As a result, the _killOperation can be processed before the original read and "miss" its intended operation.
Acceptance Criteria: Tests should ensure that we make the best effort to kill outstanding hedged reads but not require that we do so.
- is related to
 - 
                    
SERVER-58139 Avoid leaking state from NetworkInterfaceTest::CancelLocally
-         
 - Closed
 
 -         
 
- related to
 - 
                    
SERVER-65329 Ensure cursors are not leaked when cancelling in-progress operations
-         
 - Backlog
 
 -         
 - 
                    
SERVER-45866 Measure connection reuse for Hedged Reads
-         
 - Closed
 
 -         
 - 
                    
SERVER-59521 Remove TODO linked to SERVER-47602
-         
 - Closed
 
 -