[SERVER-49182] Make the op observer for "start blocking" write update MigratingTenantAccessBlockers Created: 29/Jun/20  Updated: 29/Oct/23  Resolved: 14/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-07-27
Participants:

 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.



 Comments   
Comment by Githook User [ 14/Jul/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-49182 Make the op observer for "start blocking" write update MigratingTenantAccessBlockers
Branch: master
https://github.com/mongodb/mongo/commit/25c8af4212815dc4c202c9e1c673185ad68343cf

Generated at Thu Feb 08 05:19:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.