[SERVER-72213] Recover D merge tenant access blocker on node restarts & rollbacks. Created: 16/Dec/22  Updated: 29/Oct/23  Resolved: 24/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Didier Nadeau
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-67866 Check that TenantMigrationDonorAccess... Closed
is duplicated by SERVER-72212 D shouldn’t allow Cloud to create new... Closed
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-03-06, Server Serverless 2023-03-20, Server Serverless 2023-04-03
Participants:

 Description   

Shard merge stores the list of donor tenants to be migrated in D state document. So, on node restart and rollback, the recovery procedure builds the in-memory tenant access blocker for each tenant listed in the state document.



 Comments   
Comment by Githook User [ 24/Mar/23 ]

Author:

{'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}

Message: SERVER-72213 Recover and install donor mtab for shard merge
Branch: master
https://github.com/mongodb/mongo/commit/38e6c0baa0307983caac54821c4e68a91af51a6a

Comment by Didier Nadeau [ 16/Feb/23 ]

Following discussion, the list of changes we want to do in this PR :

  • Add on tenant access blocker per tenant for shard merge donor (this allows recording per-tenant metrics)
  • Modify mtab registry to first query for tenant-specific mtab then fallback on the _ALL_ mtab
  • Properly recover mtab for _ALL_ and separate tenants
  • Add unit test
  • Update logic to remove access blockers
Comment by Didier Nadeau [ 21/Dec/22 ]

suganthi.mani@mongodb.com  We only need a slight change in a test to validate recovery of donor access blocker works in shard merge. I have included this change in SERVER-72214 and I propose we close this ticket. Let me know your thoughts.

Comment by Didier Nadeau [ 21/Dec/22 ]

suganthi.mani@mongodb.com we haven't done the change to insert tenant access blocker for each tenant given to Shard Merge yet. What is the plan on this side, do we plan to keep the "global" access blocker and also insert a per-tenant access blocker ?

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