[SERVER-69110] Consolidate stale collection/database exception handling on shards Created: 24/Aug/22 Updated: 12/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | 12/12 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Sprint: | Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Currently we have duplicated code to handle stale collection/database exceptions: This code duplication often lead to confusion and is very error prone (e.g |