-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2025-12-22, Storage Execution 2026-01-05
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, Capped Collections are not allowed to use Replicated Record IDs. This restriction was put in place as part of SERVER-89735. However, changes introduced in SERVER-82180 and SERVER-97861 have addressed the issues that initially led to this limitation. At this point, there is no longer a reason for Capped Collections to remain incompatible with Replicated Record IDs.
Proposed Solution:
- Allow Capped Collections to work with Replicated Record IDs.
- Update relevant tests to reflect the change.
- If necessary, add new tests to ensure the correct behavior of Capped Collections with Replicated Record IDs.
- is related to
-
SERVER-82180 Capped inserts on the primary can have a different natural ordering from secondaries
-
- Closed
-
-
SERVER-89735 Ensure capped:true and recordIdsReplicated:true interact correctly
-
- Closed
-
-
SERVER-97861 Serialize writes to the system.profile collection
-
- Closed
-
- related to
-
SERVER-115758 Investigate enabling replicated recordIds on internal collections.
-
- Backlog
-