[SERVER-64616] Install recipient access blocker when applying a "create" oplog entry Created: 17/Mar/22  Updated: 29/Oct/23  Resolved: 04/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File patch    
Issue Links:
Depends
depends on SERVER-61145 Start fetching donor oplog entries Closed
depends on SERVER-63122 Remove logical cloning procedure for ... Closed
is depended on by SERVER-64956 Test Shard Merge with and without ena... Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-06-27, Server Serverless 2022-07-11, Server Serverless 2022-07-25, Server Serverless 2022-08-08
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 04/Aug/22 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-64616: Install recipient access blocker when applying "create" entry
Branch: master
https://github.com/mongodb/mongo/commit/aef31ad1a0d47dcd3851161a269d5cc76f83f819

Generated at Thu Feb 08 06:00:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.