[SERVER-34580] Plumb operation time to `getMinimumVisibleSnapshot` when available Created: 19/Apr/18  Updated: 29/Oct/23  Resolved: 03/May/18

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-34639 Background indexes on primaries shoul... Closed
is related to SERVER-34777 multi-index drops are given the wrong... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-05-07
Participants:
Linked BF Score: 11

 Description   

Right now, the minimum visible snapshot will query the logical clock to publish as the "time before which readers may not query this collection". However, while the logical clock won't return a value that's too low (and cause catalog mismatch failures), it can return a value that's too high and may never exist in the oplog (particularly when the noop writer is disabled).

At least for primaries, this problem could be solved by plumbing through the actual operation time. Whether directly or via the `ReplClientInfo`.



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

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-34580 Plumb commit time to commit handlers when available
Branch: master
https://github.com/mongodb/mongo/commit/dd45579fef2bf4e212161d1e3d97666a80b08bbf

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