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

Update config.localReshardingOperations.recipient.progress_applier document following each batch of resharding's oplog application

    • Fully Compatible
    • Security 2020-10-19, Sharding 2020-11-02

      Store the largest _id value from the oplog entries applied from that donor shard in the config.localReshardingOperations.recipient.progress_applier document as the <progress {clusterTime, ts}> for that donor shard.

      {
          _id: <donor's shard ID>,
          progress: <donor1's progress {clusterTime, ts}>,
      }
      

      The largest _id value from the oplog entries applied from that donor shard should be used with {$match: {_id: {$gt: <progress {clusterTime, ts}>}}} to resume.

      When the donor shard's final oplog entry marker is applied, the config.localReshardingOperations.recipient.progress_applier document can be updated to store {_id: MaxKey} as an indicator that resuming is no longer necessary.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: