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

Reset lastCommittedOpTime to blockTimestamp after applying recipient config

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Server Serverless 2022-09-05
    • 15

      When a shard split recipient applies the recipient config locally, it should also reset the lastCommittedOpTime to the blockTimestamp. We will need to get the blockTimestamp from somewhere, current ideas are:

      • Query the TenantMigrationAccessBlockerRegistry for shard split access blockers (they can gain an accessor for their blockTimestamp)
      • Query the shardSplitDonors namespace for any documents representing an active shard split, and read the value directly from the state document

            Assignee:
            matt.broadstone@mongodb.com Matt Broadstone
            Reporter:
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: