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

Have resharding oplog fetcher resume from 'ts' component of largest _id inserted

    XMLWordPrintable

Details

    • Fully Compatible
    • Sharding 2021-02-22
    • 81
    • 1

    Description

      The largest _id value in the config.localReshardingOplogBuffer.<existingUUID>.<donorShardId> collection should be used with {$match: {ts: {$gte: <resume oplog buffer _id.ts>}}} to resume. Properties to ensure are being tested:

      1. The oplog fetcher for resharding must not trigger a duplicate key error when resuming.
      2. The oplog fetcher for resharding must not miss a document when resuming.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-49893 Create oplog fetcher for resharding

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. SERVER-51606 Handle recovery from resharding donors

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-53941 Have resharding oplog applier resume from its progress document

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              yuhong.zhang@mongodb.com Yuhong Zhang
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: