Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 3 additions & 0 deletions source/reference/limitations.txt
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,9 @@ Sharded Clusters
returns an error and stops, which requires you to start the migration
from scratch.

- ``mongosync`` doesn't support running the command :dbcommand:`transitionFromDedicatedConfigServer`
during execution.

- You must not run the :dbcommand:`moveChunk` and
:dbcommand:`moveRange` commands on the source or destination clusters.
- The shard key cannot be :ref:`refined <shard-key-refine>` while
Expand Down
12 changes: 12 additions & 0 deletions source/reference/mongosync/mongosync-behavior.txt
Original file line number Diff line number Diff line change
Expand Up @@ -179,6 +179,18 @@ primary shard to each database by means of a round-robin.
restart the migration from the start. For more information, see
:ref:`c2c-sharded-limitations`.

Config Shard Cluster
''''''''''''''''''''

Starting in 8.0, MongoDB introduces support for config shard clusters, also known
as embedded config server clusters.

``mongosync`` supports sync from dedicated config server sharded clusters to
embedded config server sharded clusters and vice versa. Additionally, ``mongosync``
supports sync from replica sets to config sharded clusters, but not vice versa.

To learn more about embedded config servers, see :ref:`config-shard-concept`.

Multiple Clusters
~~~~~~~~~~~~~~~~~

Expand Down