[SERVER-68778] Range deleter observers must ignore "not yet initialized" exceptions Created: 12/Aug/22 Updated: 29/Oct/23 Resolved: 12/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-08-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Since the op observers try to register/deregister tasks on the range deleter service, it may happen to hit the NotYetInitialized exception . Purpose of this ticket is to let them handle the exception and dassert in case of getting a different error (it must never happen, still we must prevent throwing any error in observers in production - so only dassert). |