-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-07-20, Storage Execution 2026-08-03, Storage Execution 2026-08-17
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Following the Engineering Proposal: More Efficient Replication for Container Writes, when the feature flag introduced in SERVER-130635 is enabled, we should add support for generating oplog entries in the new format. This will require adding support to OpObserverImpl and BatchedWriteContext, among potentially others to support writing oplog entries in this format.
- depends on
-
SERVER-130643 Support oplog application of batched container writes
-
- Closed
-
- is depended on by
-
SERVER-130646 Utilize batched container write format in index build spills
-
- Closed
-
- is related to
-
SERVER-132472 Batched-write applyOps packer cannot link a clustered collection's op to its index side writes, allowing torn atomic groups (e.g. timeseries bucket updates during PDIB)
-
- Closed
-
-
SERVER-130635 Create feature flag for container write oplog format optimization
-
- Closed
-
- related to
-
SERVER-130657 Utilize batched container write format in index build side writes cleanup
-
- Backlog
-
-
SERVER-130660 Enable feature flag for container write oplog format optimization
-
- Backlog
-
-
SERVER-130646 Utilize batched container write format in index build spills
-
- Closed
-
-
SERVER-130647 Utilize batched container writes in index build bulk load
-
- Closed
-
-
SERVER-130650 Utilize batched container write format in index build side writes
-
- Closed
-
-
SERVER-130655 Utilize batched container write format in index build side write drains
-
- Closed
-