[SERVER-75870] MovePrimaryRecipient needs to differentiate between user initiated and self aborts Created: 07/Apr/23 Updated: 29/Oct/23 Resolved: 17/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc0 |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Abdul Qadeer | Assignee: | Abdul Qadeer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v7.0
|
||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
To increase resilience and prevent bugs around data loss with cleanup on abort logic present in the recipient service as part of online movePrimary, we need to differentiate between user initiated and recipient initiated aborts. If the recipient is in kPrepared state, it shouldn't do self abort and should invariant. |
| Comments |
| Comment by Githook User [ 17/Apr/23 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: (cherry picked from commit 526f2bd98356f8a570e6da0c6b5c3c0e033c32ef) |
| Comment by Githook User [ 14/Apr/23 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: |