[SERVER-64618] Factor out a ShardSplitAccessBlocker to contain split-specific access blocking logic 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   

There are two major benefits to making a new ShardSplitAccessBlocker:

  • Log messages using TenantMigrationDonorAccessBlocker can be confusing when debugging a split operation, since messages relating to a "tenant migration" begin appearing from nowhere
  • Shard split allows splitting multiple tenants at the same time, so some logic could be deduplicated especially where we loop on a list of tenant ids in multiple parts of the codebase.


 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.