-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v8.0
-
CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15, CAR Team 2024-04-29
-
154
The oplog is an exception to the catalog's concurrency rules: it updates its metadata in place, and acquisitions bypass two-phase locking and two-phase commit protocols. The in-place updates are racy: a read can interleave a concurrent DDL operation like oplog resizing, and read torn oplog metadata.
- is duplicated by
-
SERVER-89168 Stash the CollectionCatalog for AutoGetOplogFastPath
- Closed
-
SERVER-63888 Make oplog collection copy-on-write instead of specially update-in-place
- Closed
- related to
-
SERVER-90643 oplog reference may be invalidated in OplogCapMaintainer loop
- Closed