Skip to content

Commit 5f9377f

Browse files
author
Sam Kleinman
committed
DOCS-908 correcting mongos connection pooling.
1 parent 11fa05d commit 5f9377f

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

source/faq/sharding.txt

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -193,10 +193,12 @@ behavior.
193193
How many connections does each ``mongos`` need?
194194
-----------------------------------------------
195195

196-
Typically, :program:`mongos` uses one connection from each client, as
197-
well as one outgoing connection to each shard, or each member of the
198-
replica set that backs each shard. If you've enabled the ``slaveOk``
199-
bit, then the mongos may create two or more connections per replica set.
196+
Typically, each client maintains as connection to
197+
:program:`mongos`. :program:`mongos` maintains a connection pool to
198+
support a single outgoing connection to each shard for. For incoming
199+
connections that direct read operations to secondaries, the
200+
:program:`mongos` will also need to maintain connects to each member
201+
of the replica set that provides the shard.
200202

201203
Why does ``mongos`` hold connections?
202204
-------------------------------------

0 commit comments

Comments
 (0)