@@ -203,7 +203,7 @@ includes the following components:
203
203
To learn more about sharded clusters, see :manual:`Sharding </sharding/>`
204
204
in the {+mdb-server+} manual.
205
205
206
- When reading from the replica set shards, mongos applies your specified read
206
+ When reading from the replica set shards, `` mongos`` applies your specified read
207
207
preference. The read preference is re-evaluated for each operation.
208
208
209
209
The following example shows how to connect to a sharded cluster and specify a
@@ -256,11 +256,11 @@ When connecting to a sharded cluster or a replica set, the {+driver-short+} uses
256
256
distribute these requests across multiple servers, which avoids overwhelming
257
257
any one server and ensures optimal performance.
258
258
259
- When connecting to a sharded cluster, the {+driver-short+} determines the closest mongos
259
+ When connecting to a sharded cluster, the {+driver-short+} determines the closest `` mongos``
260
260
instance by calculating which one has the lowest network round-trip time. Then, the driver
261
- determines the latency window by adding this mongos's average round-trip time to the
261
+ determines the latency window by adding this `` mongos`` 's average round-trip time to the
262
262
:ref:`localThresholdMS value <kotlin-sync-local-threshold>`. The driver load balances requests
263
- across up to two random mongos instances that fall within the latency window. For each request,
263
+ across up to two random `` mongos`` instances that fall within the latency window. For each request,
264
264
the driver chooses the server with the lower operation load by determining its ``operationCount``
265
265
value.
266
266
@@ -284,15 +284,15 @@ The {+driver-short+} uses the local threshold value to calculate the
284
284
latency window for server selection. This value determines the servers
285
285
that are eligible to receive read and write requests.
286
286
287
- By default, the driver uses only mongos instances or replica set members whose
287
+ By default, the driver uses only `` mongos`` instances or replica set members whose
288
288
ping times are within 15 milliseconds of the nearest server. To
289
289
distribute reads among servers with higher latencies, set the ``localThreshold``
290
290
option in a ``MongoClientSettings`` instance or the ``localThresholdMS`` option
291
291
in your connection URI.
292
292
293
293
.. note::
294
294
295
- When selecting replica set members from a single mongos instance, the
295
+ When selecting replica set members from a single `` mongos`` instance, the
296
296
{+driver-short+} ignores the ``localThresholdMS`` option. In this case, use the
297
297
:manual:`localThreshold </reference/program/mongos/#std-option-mongos.--localThreshold>`
298
298
command-line option.
0 commit comments