[SERVER-18104] Prevent mongos from starting when pointing to a standalone config server Created: 17/Apr/15  Updated: 26/Oct/20  Resolved: 23/Apr/15

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

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

Issue Links:
Related
related to SERVER-51733 config server in a docker container f... Closed
related to SERVER-17971 Improve test infrastructure to allow ... Closed
Backwards Compatibility: Major Change
Sprint: Sharding 2 04/24/15
Participants:

 Description   

Config servers must now either be the old style config triplet or a replica set



 Comments   
Comment by Githook User [ 23/Apr/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-18104 Prevent starting mongos if it's pointing to a standalone config server
Branch: master
https://github.com/mongodb/mongo/commit/4fb40170f58ffab0c03404e8fe9214fe1f3c650c

Comment by Spencer Brody (Inactive) [ 17/Apr/15 ]

Yes, that is correct. Single-server replica sets are fine (though not recommended for production)

Comment by Charlie Page [ 17/Apr/15 ]

Just to confirm, a single member replica set is fine correct? Having a minimum number of parts of a cluster is important for efficient repro's (so unrelated components don't need to be used).

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