[SERVER-64794] Catalog shard should be considered primary shard for config db Created: 22/Mar/22 Updated: 12/Apr/22 Resolved: 12/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Witten (Inactive) | Assignee: | Andrew Witten (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
In PM-2290, the catalog shard stores both user data and config data. We should consider it the primary shard for config databases. This error can be seen in jstest explain_large_bounds.js (logs here). |