Investigate changes in SERVER-114086: Explicitly replicate multikey writes in a multi-doc transaction

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Tools and Replicator
    • 35

      Original Downstream Change Summary

      This ticket introduces a new

      {op:'c'}

      oplog entry named 'setMultikeyMetadata', which explicitly sets multikey metadata.

      Description of Linked Ticket

      In multi-doc transactions, the catalog write to modify the multikey fields is done in a side transaction on the primary. On the secondary, the multikey write happens with the user operation that causes the field to be set. This makes the writes have different timestamps.

      In this ticket, we'll use the oplog entry generated from the side transaction to explicitly replicate the multikey write. Currently, the side transaction generates a no-op oplog entry. We might want to change it to a different type.

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: