[DOCS-11078] De-stress installing mongos instances on primary shards Created: 05/Dec/17 Updated: 30/Oct/23 Resolved: 26/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin LaBreck | Assignee: | Susan Kerschbaumer (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 10 weeks, 2 days ago |
| Description |
|
The documentation currently recommends running a `mongos` on the primary shard of a sharded cluster. This is not a best practice in terms of field recommendations. A quick survey of #consulting reveals that this is not a common recommendation. It seems that recommending an intermediate layer for `mongos` routers (i.e. dedicated servers) makes more sense in most cases than co-locating instances. I submitted a pull request here as an example: |