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.
Mongos Fail over did not work as expected
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.
Connection is slowly when the first config server is down
query to the router never done when the ip of the config1 lxc is down
All inserts are delayed by 5 sec when mongos wants to auto-split and the first config server is in the TCP blackhole
Creating a new connection in pymongo takes 15 seconds when the first config server is in the TCP blackhole
Host sharding config data on a replica set
Improve user cache invalidation enforcement on mongos
Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.