[SERVER-65947] MigrationDestinationManager must recover if an error occurs during release of the critical section Created: 26/Apr/22 Updated: 29/Oct/23 Resolved: 17/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc6, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Jordi Serra Torrens |
| 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 | ||||||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||||||
| Sprint: | Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 153 | ||||||||||||||||
| Description |
|
An explanation of the occurrence is in the linked BF. One solution would be to trigger migration recovery (similar to the recovery on step up) if an error is caught at this stage in the MigrationDestinationManager instead of simply clearing the MigrationDestinationManager's state. |
| Comments |
| Comment by Githook User [ 17/May/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: (cherry picked from commit 5bd946b1fcda93b27ab4c34297454c64c2b9702a) |
| Comment by Githook User [ 17/May/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |