[SERVER-49284] Biggie oplog visibility is not correct Created: 02/Jul/20  Updated: 29/Oct/23  Resolved: 13/Jul/20

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

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

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-07-13, Execution Team 2020-07-27
Participants:

 Description   

New uncommited inserts on the oplog happen with RecordIds that are lower than the currently known lowest uncommitted insert.

This leads to cursors on the oplog throwing CappedPositionLost when entries that they previously saw become hidden.

This makes replication broken on the Biggie storage engine.



 Comments   
Comment by Githook User [ 13/Jul/20 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-49284 Fix oplog visibility and replication for Biggie

Implement oplogDiskLocRegister for Biggie so we can reserve oplog holes for unordered commits.
Cursors on the oplog caches oplog visibility at the time they fork the radix tree
Branch: master
https://github.com/mongodb/mongo/commit/ae9fcd9196a8d6ca1db52a6618de51427a6669b8

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