[SERVER-50033] Make donorStartMigration command retries join the active migration Created: 30/Jul/20 Updated: 29/Oct/23 Resolved: 06/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2020-08-10 | ||||||||
| Participants: | |||||||||
| Description |
|
If the client loses the connection to the donor, the client can re-run the donorStartMigration command. Currently the retry will return without doing anything. We should update the donor's logic so that it creates and registers a TenantMigrationAccessBlocker as its first step, and retries call TenantMigrationAccessBlocker::onCompletion to wait for the migration to finish. This is a preliminary step to moving the donor's logic onto Primary-Only Service. This ticket should test that a donorStartMigration retry blocks until the migration commits or aborts. |
| Comments |
| Comment by Githook User [ 06/Aug/20 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |