Skip to content

Commit 4f2832e

Browse files
authored
DOCS-14330 Add deployment blurb back to shardedcluster page (mongodb#2363)
* DOCS-14330 Add deployment blurb back to shardedcluster page * internal feedback * XR feedback 1
1 parent b9e5c12 commit 4f2832e

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

source/core/sharded-cluster-components.txt

+7-4
Original file line numberDiff line numberDiff line change
@@ -66,10 +66,13 @@ Number of ``mongos`` and Distribution
6666
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6767

6868
Deploying multiple :binary:`~bin.mongos` routers supports high
69-
availability and scalability. For shard-level high availability, a
70-
common pattern is to place :binary:`~bin.mongos` instances on the same
71-
hardware that :binary:`~bin.mongod` instances are already running on.
72-
Another option is to embed :binary:`~bin.mongos` routers with
69+
availability and scalability. If a proxy or load balancer is between the
70+
application and the ``mongos`` routers, you must configure it for
71+
:term:`client affinity`. Client affinity allows every connection from a
72+
single client to reach the same ``mongos``. For shard-level high
73+
availability, a common pattern is to place ``mongos`` instances on the
74+
same hardware that ``mongos`` instances are already running on.
75+
Another option is to embed ``mongos`` routers with
7376
application tier infrastructure.
7477

7578
There is no limit to the number of :binary:`~bin.mongos` routers you can

source/reference/glossary.txt

+3
Original file line numberDiff line numberDiff line change
@@ -168,6 +168,9 @@ Glossary
168168

169169
Client can also refer to a single thread or process.
170170

171+
client affinity
172+
A consistent client connection to a specified data source.
173+
171174
cluster
172175
See :term:`sharded cluster`.
173176

0 commit comments

Comments
 (0)