Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Sprint:
Storage Execution 2025-12-8
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Currently when grouping writes, even if only a single write is being replicated it still wraps that write in an applyOps as if grouping multiple oplog entries together. We should make it so that if there's only one oplog entry being replicated, we skip the applyOps and replicate that write as if not grouping at all.

is depended on by

SERVER-114334 Group oplog entries by default outside of multi-document transactions

Blocked

is related to

SERVER-70544 Multideletes with a single document should not be applyOps entries

Closed

split to

SERVER-114443 Generate regular oplog entry rather than batched write applyOps for single insert

Open

SERVER-114444 Generate regular oplog entry rather than batched write applyOps for single update

Backlog

SERVER-114445 Generate regular oplog entry rather than batched write applyOps for single delete

Backlog

SERVER-114446 Generate regular oplog entry rather than batched write applyOps for single container insert

Backlog

SERVER-114447 Generate regular oplog entry rather than batched write applyOps for single container delete

Backlog

(2 split to)

Assignee:: Shin Yee Tan
Reporter:: Gregory Noma
Participants:: Gregory Noma, Shin Yee Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Nov 24 2025 03:00:23 PM UTC
Updated:: Nov 25 2025 10:46:45 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates