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

DOCSP-48515-Source-destination-balancing #678

Merged
merged 7 commits into from
Mar 26, 2025
Merged

DOCSP-48515-Source-destination-balancing #678

Changes from 3 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
43225b6
commit
mayaraman19 Mar 18, 2025
f3b55a1
feedback
mayaraman19 Mar 18, 2025
3a557ed
feedbaclk
mayaraman19 Mar 20, 2025
ba56ebb
feedback
mayaraman19 Mar 25, 2025
753ac9c
feedback
mayaraman19 Mar 25, 2025
f4b7172
link
mayaraman19 Mar 25, 2025
d319f05
contractions and ref
mayaraman19 Mar 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions source/reference/mongosync/mongosync-behavior.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,13 @@ destination cluster.
Chunk Distribution
''''''''''''''''''

.. important::

Even if the source cluster is balanced, ``mongosync`` does not
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] We can use contractions in our docs for simplicity!

Suggested change
Even if the source cluster is balanced, ``mongosync`` does not
Even if the source cluster is balanced, ``mongosync`` doesn't

Same goes for the instance below!

ensure balance of the destination cluster. To balance the destination
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since Sharding operations are not permitted during the execution of mongosync (see Limitations), you must wait until it is safe to accept writes in order to rebalance the destination cluster. See Sharded Cluster Balancer for guidance on how to rebalance the cluster.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest including the above instead of the sentence "To balance the destination [...]"

cluster, enable the destination cluster's balancer after your
migration finishes.

``mongosync`` does not preserve chunk distribution from the source to
the destination, even with multiple ``mongosync`` instances. It is not
possible to reproduce a particular pre-split of chunks from a source
Expand Down