- 
    Type:
Bug
 - 
    Resolution: Fixed
 - 
    Priority:
Major - P3
 - 
    Affects Version/s: None
 - 
    Component/s: None
 - 
    None
 
- 
        Fully Compatible
 - 
        ALL
 - 
        147
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
Force the recipient shard to refresh its routing table for the collection to ensure the transaction is not implicitly aborted when running fsync_deadlock.js in mixed version test suites (v6.0 & v5.0).
Improvements were made to chunk migration such that refreshing the routing cache forcefully was not needed in 6.0+.