[SERVER-79997] In attachCursorToPipeline when local read fails we should not catch stale config exceptions Created: 15/Aug/23 Updated: 19/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ivan Fefer | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 113 | ||||||||||||
| Description |
|
In attachCursorToPipeline we catch StaleDbVersion and StaleShardVersionError exceptions, but in theory we should not, as But if we remove them, we just fail with "Exceeded maximum number of 10 retries attempting .. sharding status of collection ... is not currently known and needs to be recovered" |
| Comments |
| Comment by Amr Elhelw [ 05/Sep/23 ] |
|
Sending to backlog since we are rewriting a lot of the sharded execution code in 8.0, and we can revisit this afterwards. |