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

Don't migrate prePostImageDoc session entries for CRUD operations outside of current migration range

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.12
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-05-20, Sharding 2019-06-03

    Description

      Problem Statement

      When migrating retryable CRUD op session entries, we generate a prePostImage oplog entry if necessary.

      Later in the process, we filter out these CRUD op entries, but not their corresponding prePostImageOplog entries. We skip the latter because the prePostImage oplog entries are created as no-ops.

      We should also filter out corresponding prePostImage oplog entries.

      Proposed Solution

      We currently have two types of no-op entries that will come through the session catalog migration pipeline. These are either sentinel oplog entries or prePostImage oplog entries. We should:

      1. Automatically let sentinel oplog entries pass through, and
      2. Check the pre- or postImage in prePostImage oplog entries to filter based on a mismatched shard key.

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              blake.oler@mongodb.com Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: