[SERVER-34701] manually set oplog visibility on rollback start Created: 26/Apr/18  Updated: 29/Oct/23  Resolved: 11/May/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34091 Oplog visibility rules can cause capp... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-05-21
Participants:

 Description   

The timestamp that oplog reads use for proper visibility is a global value that is set asynchronously. Currently, it is possible for rollback to do reads on the oplog as part of its work, and such reads may be subject to stale oplog visibility. SERVER-34091 is one example of this. To ensure no other problems are lurking, we should set the oplog visibility timestamp synchronously when rollback starts.



 Comments   
Comment by Githook User [ 11/May/18 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-34701 Wait for oplog visibily on rollback start
Branch: master
https://github.com/mongodb/mongo/commit/43c8dcee9897bb6caeec9b1f84f8105be2a19c4b

Generated at Thu Feb 08 04:37:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.