[SERVER-30662] Optionally Allow Scatter Gather Queries to Skip Failed Shards Created: 15/Aug/17 Updated: 27/Oct/23 Resolved: 16/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.16, 3.4.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Young | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
When a sharded cluster has a large number of shards, it becomes more likely that one of those shards may be experiencing a problem at any given time. When this occurs, scatter/gather queries break for the entire cluster. It would be better if MongoDB could ignore problematic shards and return the results from the rest of the cluster in such cases. This should not be the default behavior, but it should be configurable on a per-request basis for those requests that can handle incomplete results. |
| Comments |
| Comment by Andy Schwerin [ 16/Aug/17 ] |
|
The routers (mongos) already have support for this via the partial query option. |