[DOCS-8530] We need to better advise customers on how to deploy mongos Created: 08/Aug/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Steven Hand | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
We should advise decide where to deploy mongos and how many to deploy. Customers are being advised in the mongos documentation:
However, if the customer has hundreds of application servers and/or are deploying mongos with their application server, we run into situations where there are too many mongos database servers running (and thereby causing problems) and/or there are thousands of documents in the config database related to mongos. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Steven Hand [ 08/Aug/16 ] |
|
One of our customer's, Crittercism, posted a blog on why consolidating the mongos tier was important. |