[SERVER-7089] connection churn from mongos to mongod Created: 20/Sep/12 Updated: 05/Jun/13 Resolved: 13/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Sharding |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
seeing tons of sockets being opening and closed where the client to mongos pool is constant. |
| Comments |
| Comment by Randolph Tan [ 13/Nov/12 ] | ||||||||||||||
|
Confirmed that
| ||||||||||||||
| Comment by Randolph Tan [ 12/Nov/12 ] | ||||||||||||||
|
Finally got a very good idea on how this could happen - read preference. If the requests to the mongos are specified as a read preference of primary, then it will create 2 primary connections for each replica set connection object: (1) one from being called by checkMaster then stored in the _master variable when setting the shard version of the connection and |