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

Install recipient access blocker when applying a "create" oplog entry

XMLWordPrintableJSON

    • Fully Compatible
    • Server Serverless 2022-06-27, Server Serverless 2022-07-11, Server Serverless 2022-07-25, Server Serverless 2022-08-08

      In Shard Merge, the recipient adds a new access blocker when it imports a DB (SERVER-61141). It must also add a new access blocker if the donor creates a DB during the migration (between startApplyingDonorOpTime and the block timestamp). The change should be in TenantOplogApplier::_applyOplogEntryOrGroupedInserts. Patch attached. EDIT: this won't work, since we need to also (conditionally) create access blockers on secondary nodes as well, and TenantOplogApplier only runs on the primary.

        1. patch
          28 kB

            Assignee:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: