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

Make the op observer for "start blocking" write update MigratingTenantAccessBlockers

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2020-07-27

    Description

      This ticket is to make the op observer for the "start blocking" update (after the update is assigned an OpTime) get the MigratingTenantAccessBlocker for the database prefix from the MigratingTenantAccessBlockerByPrefix and:

      • on primaries, call startBlockingReadsAfter on it with the update's OpTime's Timestamp
      • on secondaries, call startBlockingWrites on it, then call startBlockingReadsAfter on the it with the update's OpTime's Timestamp

      An alternative is not do anything in the op observer on primaries (but still do the above on secondaries) and have the "data sync" function call startBlockingReadsAfter after reserving the "start blocking" write's OpTime.

      Attachments

        Activity

          People

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: