[SERVER-1448] Host sharding config data on a replica set Created: 19/Jul/10  Updated: 22/Mar/17  Resolved: 24/Sep/15

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

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 13
Labels: configserver, configsrv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-19527 Configuration directive changes for c... Closed
depends on SERVER-19537 Allow replSetInitiate on nodes not st... Closed
depends on SERVER-19543 Dynamically change config protocol in... Closed
depends on SERVER-19539 Provide data in the ismaster handshak... Closed
depends on SERVER-19545 Prohibit config server replica sets f... Closed
depends on SERVER-19547 Shard and mongos nodes should report ... Closed
Documented
is documented by DOCS-9554 Docs for SERVER-1448: Host sharding c... Closed
Duplicate
is duplicated by SERVER-9112 Config Servers as replica set Closed
is duplicated by SERVER-18380 Make mongos use read-after-optime whe... Closed
is duplicated by SERVER-13530 Check existence of "version" collecti... Closed
is duplicated by SERVER-19884 All config server crash Closed
Related
related to SERVER-1658 make adding/changing config servers easy Closed
related to SERVER-11980 Improve user cache invalidation enfor... Closed
related to SERVER-22936 Zero-downtime upgrade from mirrored (... Closed
related to SERVER-3698 When mongos reports config servers no... Closed
is related to SERVER-17617 One config server being down can bloc... Closed
is related to SERVER-19696 Don't allow using a replica set as th... Closed
is related to SERVER-5960 mongos config server order should not... Closed
is related to SERVER-3353 ismaster should return a msg for a co... Backlog
is related to SERVER-2512 don't allow adding a config server as... Backlog
is related to SERVER-5188 Load balance reads across config servers Closed
is related to SERVER-5119 why 1 or 3 config server ? why not 2 ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 8 08/28/15
Participants:

 Comments   
Comment by Githook User [ 18/Nov/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-21320 When no port is provided for a configdb argument to mongos, assume
port 27019.

This is the behavior for mongodb 3.0 and prior, which was inadvertently removed
while refactoring sharding code in preparation for SERVER-1448.
Branch: master
https://github.com/mongodb/mongo/commit/5d22dc0c4ea4e611464c75b356f52741184359e6

Comment by Michael Saffitz [ 29/May/13 ]

+1 on this, and specifically addressing the issue raised in SERVER-5960. We're using chef to automate deployment of our cluster. For reasons not entirely clear to me yet, somehow the order-- but nothing else-- of the config servers internal to the config server has changed. This then has broken every mongos connecting to it. It'd be really nice if the order could be normalized in the comparison.

Comment by Dwight Merriman [ 19/Aug/12 ]

when this is done in the future let's be sure that one cannot accidentally add a config server to a different replica set – it will look eligible perhaps. perhaps the setname protects that already.

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