See comment on SERVER-11980. User reported that having one config server down meant than when the user cache was invalidated repopulating it would take over 10 seconds.
- is duplicated by
-
SERVER-17668 Mongos Fail over did not work as expected
- Closed
-
SERVER-21007 When the first config server's network encounter problem(ip can't be ping through), the mongos will be very very slow, seem like hang problem.
- Closed
-
SERVER-21496 Connection is slowly when the first config server is down
- Closed
- is related to
-
SERVER-22486 query to the router never done when the ip of the config1 lxc is down
- Closed
- related to
-
SERVER-16690 All inserts are delayed by 5 sec when mongos wants to auto-split and the first config server is in the TCP blackhole
- Closed
-
SERVER-16691 Creating a new connection in pymongo takes 15 seconds when the first config server is in the TCP blackhole
- Closed
-
SERVER-1448 Host sharding config data on a replica set
- Closed
-
SERVER-11980 Improve user cache invalidation enforcement on mongos
- Closed