[SERVER-49184] Make new database creation set the database's MigratingTenantAccessBlocker to the corresponding one in MigratingTenantAccessBlockerByPrefix Created: 30/Jun/20  Updated: 06/Dec/22  Resolved: 21/Jul/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49171 [optimization] Optimize access to Mig... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2020-07-13, Sharding 2020-06-29
Participants:

 Description   

Modify theĀ DatabaseHolder::openDb method to check if the new database's name matches any prefix in MigratingTenantAccessBlockerByPrefix (by calling MigratingTenantAccessBlockerByPrefix::get with the database's name), and if so, set the new Database's shared_ptr<MigratingTenantAccessBlocker> decoration to the returned shared_ptr<MigratingTenantAccessBlocker>.

Note that there is no durable concept of a database. A database is created by being "opened", and durable state for it is only created when a collection in it is created.



 Comments   
Comment by Esha Maharishi (Inactive) [ 21/Jul/20 ]

This is only necessary if the optimization in SERVER-49171 is implemented, and can be re-opened if so.

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