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

[RRFaM] Have update path write to config.image_collection

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.25, 4.2.15, 4.4.7, 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.4, v4.2, v4.0
    • Repl 2021-05-17

      When the RRFaM behavior is enabled:

      • A primary executing the update can add an update to the SessionTxnRecord within the same WUOW.
      • A secondary applying the update can also add an update to the SessionTxnRecord within the same WUOW.
        • Right now the UpdateResult does not return the pre/post image. This ticket should expose that API.
        • However the update predicate must include the clause: `{txnNum: {$lt: <updated txnNum>`}}.
      • Remove noop oplog entry writes for FaM updates
      • Take care to leave the upsert path alone (pre/post images are already trivially replicated)
      • Collections configured to always store preImages must continue to write noop pre-image oplog entries.
        • A findAndModify against these collections should avoid also saving the preImage into a config.transactions document.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: