[SERVER-9112] Config Servers as replica set Created: 25/Mar/13  Updated: 28/Mar/13  Resolved: 25/Mar/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Norberto Fernando Rocha Leite (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: sharded-cluster
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-1448 Host sharding config data on a replic... Closed
Participants:

 Description   

The config servers have a crucial role over sharding since they hold the mapping information of all moving pieces of a shard cluster.
For several use cases the current behavior of config servers can be quite limiting due to 2 aspects:

  • Strick number of members
    • can impact multiple datacenter deployments
    • specially on slow networks
  • Failover of members
    • needs to have all 3 always online otherwise the cluster may encounter problems booting up mongos's

Due to historic and mathematical reasons the config servers have the current hard number of 3 members.
Setting them as replicas with enforced Write Concerns for balancer locking and migration operations we can achieve a more flexible shard cluster.
Also the current hard setting creates some confusion on clients and generates a bit of unrest while configuring a sharding environment.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 25/Mar/13 ]

See SERVER-1448, but the answer is most likely no.
There are other considerations that make replica sets a bad choice.

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