[SERVER-55053] Treat CallbackCanceled as a retryable error in TenantMigrationRecipientService Created: 09/Mar/21 Updated: 29/Oct/23 Resolved: 16/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_other_required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2021-03-22 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
In PrimaryOnlyService onStepDown, we cancel the token first which would give a CallbackCanceled error before each instance is interrupted. So the error handling gets tricky because CallbackCanceled is not a retryable error. |
| Comments |
| Comment by Githook User [ 16/Mar/21 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |