-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2022-07-11, Execution Team 2022-07-25, Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19, Execution Team 2022-10-03, Execution Team 2022-10-17, Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2022-12-26, Execution Team 2023-01-09
Unreplicated capped collections do not serialize writes (see SERVER-21646), which means that tailable cursors can miss writes that commit in a different order than they were inserted.
This problem has essentially existed since we implemented document-level locking in 3.0.
Instead of also serializing writes to capped local collections, which would affect performance of inserts into the system.profile collection, I propose that we ban the usage of tailable cursors on unreplicated capped collections since they never worked correctly anyways.
- depends on
-
SERVER-68271 Trigger Collection instantiation when reading PIT earlier than last DDL timestamp in Collection
-
- Closed
-
- is related to
-
-
- Backlog
-
-
SERVER-97861 Delete CappedSnapshots machinery
-
- Blocked
-