-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
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, Execution Team 2023-01-23
Batched operations (see BatchedWriteContext) are currently limited to replicating as a single oplog entry. This places the responsibility of limiting the operations in a batched write on the caller. It would be nice to re-use the chained applyOps format used for large multi-document transactions to format large batched operations in a similar manner. Callers would no longer be constrained by the single applyOps format. However, for performance reasons, callers should still be aware of the implications of allowing unbounded set of operations to be batched and handle these issues accordingly.
This ticket is limited to having the primary emit a chain of applyOps oplog entries representing a large batched write. Processing this chain of applyOps oplog entries on the secondary will be addressed in a follow-up ticket.
This behavior will be guarded by a feature flag.
- is duplicated by
-
SERVER-70572 support applyOps oplog entry chaining for BatchedWriteContext
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-