Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.6.0
Affects Version/s: None
Component/s: Sharding
Labels:
- cap-ticket-needed
- revisit

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Currently, mongos closes one connection at a time, even though it can "tell" that every connection to that shard is going to be bad. It could mark them all as failed and so not return as many error to the client.

Leads to Assertion: 13633:error querying server errors (for Google-ability).

depends on

SERVER-9041 proactively detect broken connections detected by the network

Closed

is duplicated by

SERVER-4997 Mongos not clearing stale connections

Closed

is related to

SERVER-9041 proactively detect broken connections detected by the network

Closed

SERVER-7573 Add tests for network connectivity loss, especially in sharded systems.

Closed

related to

SERVER-9788 mongos does not re-evaluate read preference once a valid replica set member is chosen

Closed

SERVER-7629 Make DBClientReplicaSet draw connections from a pool

Closed

(1 related to)

Assignee:: Randolph Tan
Reporter:: Kristina Chodorow (Inactive)
Participants:: Ajay Batheja, auto, Ben Becker, Greg Studer, Kristina Chodorow, Michael DelNegro, Randolph Tan, Tito George
Votes:: 21 Vote for this issue
Watchers:: 30 Start watching this issue

Created:: Jan 18 2012 12:22:02 AM UTC
Updated:: May 24 2017 04:04:06 PM UTC
Resolved:: Jul 01 2014 04:57:58 PM UTC
Confidence Status Last Update:: 17/Nov/12 7:50 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates