[SERVER-85522] Add a warning to view creation if the collection lives outside the dbPrimary Created: 22/Jan/24 Updated: 02/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
View performance is substantially worse on unsharded collections if the unsharded collection lives outside the dbPrimary (since views are located on the dbPrimary). SERVER-85230 will prevent the balancer from moving collections that already have views, but this does not prevent the user from creating a view after the collection has been moved off of the primary. This ticket is to issue a warning if the user creates a view on an unsharded collection living outside the dbPrimary telling the user about the decreased performance and suggesting using moveCollection to return the collection to the dbPrimary. |