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

SessionUpdateTracker should ignore no-op entries for pre/post image oplogs

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Sharding 2019-03-11
    • Linked BF Score:
      13

      Description

      These pre/post entries is only valid if paired with the corresponding update/delete oplog entries. Since the update/delete oplog entry always comes after the pre/post entry and both of these entries contain the same amount information necessary to properly replicate the config.transactions table, the pre/post entry should be ignored. Otherwise, it can create a situation where the secondary replication would mistakenly think that write was performed if sees the pre/post entry even though the update/delete oplog entry was removed due to replication rollback.

      Note: it should not ignore no-op entries generated during session migration.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: