[SERVER-8155] Provide single control interface for cluster Created: 11/Jan/13 Updated: 06/Dec/22 Resolved: 19/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | eHarmony Matching | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
When configuring a cluster, some commands can be executed on any mongod, others only on a primary mongod, and others only on a mongos. All of these separate endpoints make the overall task much more complicated than it should be. It would be much better if we could connect one time and issue all of the commands we need to. Ideally, mongos would be this interface, because we have to provision and manage these nodes anyway, and mongos's job is already to dispatch commands to other nodes as appropriate. |