- 
    Type:
Bug
 - 
    Resolution: Fixed
 - 
    Priority:
Major - P3
 - 
    Affects Version/s: 4.1.3
 - 
    Component/s: None
 
- 
        Fully Compatible
 - 
        ALL
 - 
        Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-04-08, Sharding 2019-04-22, Sharding 2019-05-06, Sharding 2019-05-20
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
otherwise, it is possible for another thread trying to perform a refresh as a response to being invalidated will not see the side effect that cause the invalidation.
- is related to
 - 
                    
SERVER-36493 Invalidate in-memory prepared transaction state on replication rollback
-         
 - Closed
 
 -         
 - 
                    
SERVER-38576 Ban direct writes to transaction table in replset
-         
 - Closed
 
 -