[SERVER-18619] Explicitly disallow the config server replica set from being added as a shard Created: 21/May/15  Updated: 09/Aug/15  Resolved: 09/Aug/15

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

Type: Task Priority: Major - P3
Reporter: Cailin Nelson Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-19545 Prohibit config server replica sets f... Closed
Sprint: Sharding 8 08/28/15
Participants:

 Description   

In MongoDB 3.2, config servers may be a replica set. Hooray!

Please explicitly prevent users from doing the following:

  • Create a cluster whose config servers are banana/a:27017,b:27017,c:27017
  • Then do sh.addShard( "banana/a:27017" )

Since addShard occurs via a mongos and the mongos must be aware of the current configuration of the config servers, it seems possible to prevent this.



 Comments   
Comment by Cailin Nelson [ 21/May/15 ]

I imagine changing the way things are would be intrusive and difficult, so please consider this request to apply only to the new world of config server replica sets. In the new world I'm hoping its not too hard to add this new rule.

Comment by Scott Hernandez (Inactive) [ 21/May/15 ]

This should not disallow using non-replica set config server(s) as shards, which is currently allowed, correct?

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