Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.2.0-rc4
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding A (10/09/15), QuInt B (11/02/15), TIG B (10/30/15), QuInt C (11/23/15)

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

(3 related to)

Assignee:: Kaloian Manassiev

Reporter:: Spencer Brody (Inactive)

Participants:: Kaloian Manassiev, Max Hirschhorn, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: Mar 16 2015 09:22:10 PM UTC

Updated:: Feb 05 2016 03:21:38 PM UTC

Resolved:: Nov 20 2015 04:07:16 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates