[SERVER-55502] Investigate capped collection tailing behavior on local collections Created: 24/Mar/21  Updated: 06/Dec/22

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

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Capped collections on the local database don't use so-called "metadata lock" that serializes write operations. This may be a problem for tailable cursors, which could skip over "holes". That is, the tailable cursors may skip over records that have not yet committed or are committed in a later snapshot.

The oplog solves this problem by only showing records that are guaranteed to have no uncommitted writes before them.


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