This project will introduce a new oplog entry to explicitly replicate new multikey paths introduced in the context of a multi-document transaction. mongosync, mongomirror and mongodump/mongorestore will ignore this oplog entry. The server guarantees that if the oplog entry’s event won’t show up in the change stream or it is skipped when reading the raw oplog, the multikey metadata is maintained correctly.

Description of Linked Ticket

Summary

Set multikey metadata using a timestamp that is consistent among replica set members.

Motivation

Ensuring that the same multikey writes are performed on the primary and standby with the same timestamp enables stronger WiredTiger assertions for disaggregated storage, such as WT-15476.

Documentation

Docs Update
Technical Design
Scope