[SERVER-33337] Shards should error if the config server doesn't have metadata for a namespace Created: 14/Feb/18 Updated: 27/Oct/23 Resolved: 02/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | MaxH, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
with the exception of databases that are only local to the shard (like local, admin, and some config). This ticket would include the work to ensure that proper metadata entries exists in config.collections, config.chunks as well as the local storage versions of it before serving requests for said collection. MapReduce would need special handling, as it creates temp output collections locally, and then renames them to the final collection at the end. |
| Comments |
| Comment by Max Hirschhorn [ 02/Nov/22 ] |
|
This ticket was originally part of PM-1051 but is no longer necessary. |