[SERVER-68985] Tenant migration donor should set _forgetMigrationDurablePromise even on failover Created: 19/Aug/22 Updated: 29/Oct/23 Resolved: 14/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Server Serverless 2022-09-05, Server Serverless 2022-09-19, Server Serverless 2022-10-03, Server Serverless 2022-10-17, Server Serverless 2022-10-31, Server Serverless 2022-11-14, Server Serverless 2022-11-28, Server Serverless 2022-12-12, Server Serverless 2022-12-26 | ||||||||
| Participants: | |||||||||
| Description |
|
Consider a case where the donor failover happens after the donor state doc is marked as garbage collectable but before resolving _forgetMigrationDurablePromise as ok. This would result, in new primary to go into this code path, resulting in new primary to resolve the _forgetMigrationDurablePromise only after the state doc is deleted rather than after marking state doc as garbage collectable, causing donorForgetMigration to wait for a long time (the garbage collection delay) before returning. |
| Comments |
| Comment by Githook User [ 14/Dec/22 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: _forgetMigrationDurablePromise is now set in the continuation after marking the state doc as garbage collectable, so that if the node is resuming on stepping up to primary and the state doc is already marked garbage collectable, the node will still set the promise.collectable even for donor failover |