[SERVER-67574] Ensure TenantOplogBatcher exceptions for repl state change are caught Created: 27/Jun/22 Updated: 29/Oct/23 Resolved: 30/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christopher Caplinger | Assignee: | Christopher Caplinger |
| 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 | ||||
| Sprint: | Server Serverless 2022-07-25 | ||||
| Participants: | |||||
| Linked BF Score: | 154 | ||||
| Description |
|
Ensure TenantOplogBatcher exceptions for repl state change (and others) are caught and forwarded. also avoid throwing and/or uassert, _doStartup_inlock is marked noexcept. also should clean up the same noexcept issue in the TenantOplogApplier. |
| Comments |
| Comment by Githook User [ 30/Jun/22 ] |
|
Author: {'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}Message: |