Add resharding retryability tests for writes during primary-driven index build

XMLWordPrintableJSON

    • Type: Engineering Test
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2026-06-22, Storage Execution 2026-07-06, Storage Execution 2026-07-20, Storage Execution 2026-08-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The resharding oplog cloner must chain-walk kApplyOpsAppliedAtomically entries, BatchPreparer must unroll them into per-statement entries, and session application must record them in config.transactions on the recipient. Verify that retries are noops before, during, and after resharding (with IncompleteTransactionHistory expected post-resharding, matching existing resharding retryable write behavior).

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

              Created:
              Updated:
              Resolved: