[COMPASS-6208] Investigate changes in PM-2290: Make dedicated config servers optional for sharded clusters Created: 17/Oct/22 Updated: 12/Jun/23 Resolved: 03/May/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | COMPASS-5987 | ||||
| Documentation Changes: | Not Needed | ||||
| Description |
|
Original Downstream Change Summary The design document has more details about the changes which is being reviewed in WRITING-8015. User-Facing Syntax Changes API Changes Config File Changes Description of Linked Ticket+underlined text+ Epic Summary SummaryWe will make dedicated config servers optional for sharded clusters. Customers will have the option to designate a special shard that will hold both user data and config data. For one-shard clusters on Atlas, the shard will automatically be a special shard with both the shard role and config role. MotivationEliminating dedicated config servers will reduce both the cost and the architectural complexity involved in single-shard sharded clusters. On Atlas, a single-shard M30 sharded cluster costs TWICE as much as an M30 replica set. This project would bring cost parity to single-shard clusters on Atlas and will make it easier for customers to start out with a sharded cluster or switch to a sharded cluster. It also supports other use-cases:
Cast of Characters
DocumentationProduct Description |
| Comments |
| Comment by PM Bot [ 12/Jun/23 ] |
|
Fix Version updated for upstream PM-2290: |
| Comment by Le Roux Bodenstein [ 03/May/23 ] |
|
This does not affect dev tools. |