[SERVER-64619] Don't require a connection string in tenant access blocker constructor Created: 17/Mar/22  Updated: 06/Dec/22  Resolved: 08/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Matt Broadstone Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Serverless
Participants:

 Description   

Currently the TenantMigrationDonorAccessBlocker requires passing in a recipientConnectionString to its constructor. In shard split this becomes difficult because we need to consult the local replset config in order to build that connection string each time it's required. It's impossible to do that on recovery, since the access blocker recovery code is run before a local config is installed. This ticket will cover making this field optional, since it's only used to generate a debug string.

This is a stop-gap fix until we implement SERVER-64618, which will be a more comprehensive fix for shard split access blocking.



 Comments   
Comment by Matt Broadstone [ 08/Jun/22 ]

Would be nice-to-have in terms of improving logging, but closing since we lack time in the project to complete the work.

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