Add oplog shape and secondary apply correctness tests for writes during primary-driven index build

XMLWordPrintableJSON

    • Type: Engineering Test
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2026-06-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a single-statement retryable write occurs during PDIB, the resulting applyOps oplog entry must have multiOpType: 2 (kApplyOpsAppliedAtomically), carry lsid/txnNumber/prevOpTime, and contain both the user operation and container side write inner ops. The config.transactions entry on both primary and secondary must not have state: "committed" (which would indicate the SessionUpdateTracker misidentified it as a multi-document transaction). Primary and secondary data must match after replication.

            Assignee:
            Shin Yee Tan
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: