-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
Fully Compatible
-
Sharding 8 08/28/15
- depends on
-
SERVER-19527 Configuration directive changes for config servers as replica sets
- Closed
-
SERVER-19537 Allow replSetInitiate on nodes not started with --replSet
- Closed
-
SERVER-19543 Dynamically change config protocol in mongos and shard servers
- Closed
-
SERVER-19539 Provide data in the ismaster handshake to identify the config server protocol
- Closed
-
SERVER-19545 Prohibit config server replica sets from being added as shards
- Closed
-
SERVER-19547 Shard and mongos nodes should report their config server connection string in serverStatus
- Closed
- is duplicated by
-
SERVER-9112 Config Servers as replica set
- Closed
-
SERVER-18380 Make mongos use read-after-optime when consulting config servers
- Closed
-
SERVER-13530 Check existence of "version" collection periodically
- Closed
-
SERVER-19884 All config server crash
- Closed
- is related to
-
SERVER-17617 One config server being down can block read operations on config data for seconds
- Closed
-
SERVER-19696 Don't allow using a replica set as the config server unless it has configServer:true in its replica set config
- Closed
-
SERVER-5960 mongos config server order should not matter
- Closed
-
SERVER-3353 ismaster should return a msg for a config server
- Backlog
-
SERVER-5188 Load balance reads across config servers
- Closed
-
SERVER-2512 don't allow adding a config server as a shard
- Closed
-
SERVER-5119 why 1 or 3 config server ? why not 2 or 4 5 . can u explain it.
- Closed
- related to
-
SERVER-1658 make adding/changing config servers easy
- Closed
-
SERVER-11980 Improve user cache invalidation enforcement on mongos
- Closed
-
SERVER-22936 Zero-downtime upgrade from mirrored (SCCC) to replica set (CSRS) config servers
- Closed
-
SERVER-3698 When mongos reports config servers not in sync, also report which to sync from
- Closed