[SERVER-3426] allow sharing of config servers between clusters Created: 13/Jul/11  Updated: 06/Dec/22  Resolved: 03/Dec/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: New Feature Priority: Minor - P4
Reporter: Antoine Girbal Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Assigned Teams:
Sharding
Participants:

 Description   

many users have more than 1 db cluster because they process data with different requirements (small &
very reliable vs big & transient).
In one instance a user has 7 clusters, which means they need to spawn 21 config servers, which is pain for admin and backup.
It would be beneficial to be able to share config servers between clusters since the data & rps requirement is low.
For example instead of the "config" db name, the name could include the cluster name and each cluster would have its own db.
Cluster name can be passed to mongos command along the configdb hostnames.



 Comments   
Comment by Tommaso Tocci [ 03/Dec/21 ]

This solution is fairly complicated to implement because it requires handling namespace conflicts between different clusters. Instead we are exploring the possibility of removing the needs of a dedicated replicaset for the config server.

Generated at Thu Feb 08 03:03:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.