Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

Commit c08bcc7

Browse files
committed
additional review
1 parent 89268df commit c08bcc7

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

source/reference/mongosync/mongosync-behavior.txt

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -381,16 +381,17 @@ Latency between ``mongosync`` and destination shards
381381
slower the sync.
382382

383383
Latency between destination shards
384-
Mongosync writes operations and updates its own metadata on the
385-
destination cluster in batches in a transaction. This can result in
384+
``mongosync`` runs operations and updates its own metadata in batches
385+
in a transaction on the destination cluster. This can result in
386386
cross-shard transactions, which may be more costly if the shards are
387387
far apart.
388388

389-
Latency between the nodes of each individual replica set on the source or destination
389+
Latency between the nodes of any replica set on the source or destination cluster
390390
``mongosync`` uses :writeconcern:`"majority"` writes and
391391
:readconcern:`"majority"` reads, which require acknowledgement from
392-
multiple nodes in a replica set. If the majority of these nodes aren't
393-
in the same region, there will be negative performance implications.
392+
multiple nodes in a replica set, including shard-backing replica
393+
sets. If the majority of these nodes aren't in the same region, there
394+
will be negative performance implications.
394395

395396

396397
Learn More

0 commit comments

Comments
 (0)