Container ops in an applyOps chain commit at their per-entry optime instead of the chain commit optime

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2026-06-08, Storage Execution 2026-06-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On secondaries this can split container ops from the operations they were written with and crash apply. Commit them at the chain commit timestamp like other ops.

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

              Created:
              Updated:
              Resolved: