[SERVER-62855] MigrationDestinationManager should not blindly dereference _sessionMigration on recovery error handling Created: 21/Jan/22 Updated: 29/Oct/23 Resolved: 24/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | |||||
| Sprint: | Sharding EMEA 2022-01-24 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
If a new migration recipient primary steps-up and then fails (e.g. stepsdown too) during migration recovery, indeed _migrateThread will throw. On cleanup, it will dereference _sessionMigration, which if that node instance had never been the recipient of a migration, will be nullptr. |
| Comments |
| Comment by Githook User [ 24/Jan/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |