[SERVER-61964] FCBIS needs to handle transient error when opening backup cursor Created: 09/Dec/21 Updated: 29/Oct/23 Resolved: 02/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| 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: |
v5.2
|
||||||||||||||||||||
| Sprint: | Replication 2022-02-07 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 21 | ||||||||||||||||||||
| Description |
|
If a WT checkpoint happens while opening a backup cursor, opening the backup cursor will fail with error 50915. FCBIS should handle this error by retrying. (Alternately we could retry internally within backup_cursor_service and never return 50915). |
| Comments |
| Comment by Githook User [ 02/Feb/22 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by Githook User [ 02/Feb/22 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by A. Jesse Jiryu Davis [ 21/Jan/22 ] |
|
SGTM. I guess the error code is defined in the public repo, thrown from enterprise, and caught in the public repo? Seems ok. |