[SERVER-71618] Investigate non auto-retry commands on StaleConfig error Created: 25/Nov/22 Updated: 07/Mar/23 Resolved: 07/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Sprint: | Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23 | ||||
| Participants: | |||||
| Description |
|
We have received recently some complaints about the non-retry behaviour on StaleConfig error when running a count command.
|
| Comments |
| Comment by Silvia Surroca [ 07/Mar/23 ] |
|
The assumption described on the Jira description is wrong since the retry on StaleConfig error is handled on the service_entry_point, which is on a higher level than the scatter-gather machinery. So, the fact that scatter-gather is not retrying on StaleConfig errors is correct since that exception must bubble up until being handled by the service_entry_point. Closing this ticket as Done since the investigation has concluded.
PD: thanks tommaso.tocci@mongodb.com for reaching me out |