[DOCS-11624] Update atlas mongos configuration docs Created: 16/Apr/18 Updated: 08/Jun/18 Resolved: 20/Apr/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 42 weeks, 5 days ago | ||||||||
| Story Points: | 0.1 | ||||||||
| Description |
|
https://docs.atlas.mongodb.com/create-new-cluster/#scale-your-replica-set-to-a-sharded-cluster
This is no longer true. Atlas deploys a mongos on every shard server. This allows us to have geo-affinity to mongos from user applications from whichever region they are in. When connecting from a driver, all mongos are included in the connection string. When connecting from the shell, only the first mongos is cc: cory.mintz |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 20/Apr/18 ] |
| Comment by Ravind Kumar (Inactive) [ 18/Apr/18 ] |
|
AH, I misread. This makes sense, thanks! |
| Comment by Cory Mintz [ 18/Apr/18 ] |
|
No, there is one on every server. NumShards * ReplicationFactor. |
| Comment by Daniel Pasette (Inactive) [ 18/Apr/18 ] |
There is now one mongos on every shard server (all nodes in each shard). This allows the driver to connect to the shards that are "nearest" to it in a multi-region sharded cluster. Drivers will balance operations across all mongos which are within it's "latency window" as measured by ping time. |
| Comment by Ravind Kumar (Inactive) [ 18/Apr/18 ] |
|
pasette cory.mintz is this to say that the number of `mongos` instances is now equal to the number of shards in your sharded cluster? |