[SERVER-4706] when a socket between mongos and mongod fails, close all connections immediately Created: 18/Jan/12 Updated: 24/May/17 Resolved: 01/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 21 |
| Labels: | cap-ticket-needed, revisit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
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). |
| Comments |
| Comment by Greg Studer [ 01/Jul/14 ] |
|
This issue has become a bit of a hodgepodge: Fixed in v2.4 ( |
| Comment by Randolph Tan [ 08/Jul/13 ] |
|
Hi, Currently, there is no effective way of clearing the entire pool of bad connections. On the other hand, there is a fix in the master branch ( Thanks! |
| Comment by Tito George [ 04/Jul/13 ] |
|
Is there any recommended workaround for this, Or restarting mongos is the only option? Is there anyway in mongo to remove stale connections. I ran into the below error while doing a fail-over test on one of the replica set. I hope this is the same issue discussed here. Caused by: com.mongodb.MongoException: DBClientBase::findN: transport error: xx-xx-xx-xx.xxx:27018 ns: admin.$cmd query: { setShardVersion: "database.users", configdb: "xxx-xxx-xxx-xxx.xxx:27019,xxx-xxx-xxx-xxx.xxx:27019,xxx-xxx-xxx-xxx.xxx:27019", version: Timestamp 2000|0, versionEpoch: ObjectId('51d55747c0b7226ddb8f342d'), serverID: ObjectId('51d3d8e6c0b7226ddb8efd1d'), shard: "rs0", shardHost:"rs0/xxx-xxx-xxx-xxx.xxx:27018,xxx-xxx-xxx-xxx.xxx:27018,xxx-xxx-xxx-xxx.xxx:27018" }at com.mongodb.MongoException.parse(MongoException.java:82) ~[mongo-java-driver-2.9.3.jar:na] |
| Comment by auto [ 18/Dec/12 ] |
|
Author: {u'date': u'2012-12-12T23:40:50Z', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Additional fix for query/insert. |
| Comment by auto [ 21/Nov/12 ] |
|
Author: {u'date': u'2012-11-21T16:54:06Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: Fix test for gle doesn't work with mongos ( |
| Comment by auto [ 19/Nov/12 ] |
|
Author: {u'date': u'2012-11-19T03:45:03Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |
| Comment by auto [ 18/Nov/12 ] |
|
Author: {u'date': u'2012-11-18T23:15:19Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: |
| Comment by Randolph Tan [ 17/Nov/12 ] |
|
If |
| Comment by auto [ 17/Nov/12 ] |
|
Author: {u'date': u'2012-11-17T07:19:09Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: buildbot compile fix for |
| Comment by auto [ 17/Nov/12 ] |
|
Author: {u'date': u'2012-11-17T07:01:26Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: buildbot compire error fix for |
| Comment by Randolph Tan [ 17/Nov/12 ] |
|
Note: first commit only handles direct connections. Connections to replica sets are special since they encapsulate multiple connections within them and can do auto retry in certain cases (for example, in slaveOk reads). |
| Comment by auto [ 17/Nov/12 ] |
|
Author: {u'date': u'2012-11-05T17:05:39Z', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Ben Becker [ 06/Aug/12 ] |
|
Hi Mike, That's correct; this feature was pushed to v2.3.0. Regards, |
| Comment by Michael DelNegro [ 06/Aug/12 ] |
|
Can you please confirm that this is not fixed in the 2.2.X codeline? Thanks, |
| Comment by Ben Becker [ 14/May/12 ] |
|
Hi Ajay, This one is next on my plate. It will be in the v2.1.2 release, which is currently scheduled for the end of the month. Regards, |
| Comment by Ajay Batheja [ 14/May/12 ] |
|
Any new update on this? |