Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70572

support applyOps oplog entry chaining for BatchedWriteContext

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Execution Team 2022-12-12, Execution Team 2023-02-20, Execution Team 2022-12-26, Execution Team 2023-01-09, Execution Team 2023-02-06, Execution Team 2023-03-06

      A WriteUnitOfWork with batched writes enabled may emit at most one applyOps oplog entry currently. We would like to re-examine this limitation and look at reusing some of the formatting changes we did for large multi-doc transactions, which emits a chain of applyOps oplog entries to be interpreted as one logical unit for secondary oplog application.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: