[SERVER-53991] donorAbortMigration should not try to abort migration after the donor has written commit decision Created: 22/Jan/21 Updated: 29/Oct/23 Resolved: 26/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Jason Zhang |
| 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 | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2021-02-08 | ||||
| Participants: | |||||
| Linked BF Score: | 55 | ||||
| Description |
|
It is illegal and unsafe to transition to aborted state after the commit decision has been written so we shouldn’t call checkIfReceivedDonorAbortMigration here after we have already written commit decision. |
| Comments |
| Comment by Githook User [ 26/Jan/21 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |