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

Handle duplicate oplog entries in transaction write history for findAndModify

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding
    • Fully Compatible
    • Sharding 2017-10-02

    Description

      findAndModify retry design is based on storing the post/pre-image of the operation on a separate no-op oplog entry along with the actual write oplog entry. In normal cases, the retry logic can expect to see only a max of 2 oplog entries. However, due of migrations, there can be duplicate oplog entries (for the same write, but different timestamp). The findAndModify retry logic should be able to handle this.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: