Single-statement retryable writes (insert, update, delete) issued while a primary-driven index build is active get packed into applyOps entries with kGroupForAtomicWrite. Verify that retrying each write shape is a noop on the same primary, and that retries remain idempotent after failover to a secondary that applied the writes from the oplog.
- fixes
-
SERVER-129184 Add oplog shape and secondary apply correctness tests for writes during primary-driven index build
-
- Closed
-
- is related to
-
-
- Closed
-
- split from
-
SERVER-128618 Integration testing for handling large concurrent writes during PDIB
-
- Open
-