[SERVER-16060] better progress tracking for stale config errors in mongos reads/commands Created: 10/Nov/14 Updated: 06/Dec/22 Resolved: 13/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
For very expensive and long-running aggregation operations (query/m-r/agg) in very active clusters, the retry logic in parallel.cpp may need to be more aggressive. The default number of retries in this case may not be appropriate - explicit progress tracking is probably a better approach. See intermittent error: |