[SERVER-45280] Invalidate default read write concern cache on replication rollback Created: 20/Dec/19  Updated: 29/Oct/23  Resolved: 16/Jan/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-13, Sharding 2020-01-27
Participants:

 Description   

After a rollback (to a timestamp or via refetch), the default read write concern cache should be invalidated.



 Comments   
Comment by Githook User [ 16/Jan/20 ]

Author:

{'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-45280 Invalidate default read write concern cache on replication rollback
Branch: master
https://github.com/mongodb/mongo/commit/334b46b17d0d14bea880741d539a8b00480e2fde

Generated at Thu Feb 08 05:08:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.