[SERVER-61581] Determine TenantMigration{Donor,Recipient}Service coordination mechanism Created: 17/Nov/21 Updated: 27/Oct/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Christopher Caplinger | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
Each TenantMigrationDonorService and TenantMigrationRecipientService must prevent a merge if there is an existing donor or recipient shard merge in progress. Currently, each service has an independent mutex. |
| Comments |
| Comment by Suganthi Mani [ 03/Mar/23 ] |
|
We solved this problem by acquiring serverless lock at the start of migration to enforce mutual exclusion - https://jira.mongodb.org/browse/SERVER-65315 |