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

DOCSP-48609-add-mongosync-notes #691

Merged
merged 8 commits into from
Mar 27, 2025
Merged

DOCSP-48609-add-mongosync-notes #691

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
52e30e2
DOCSP-48609-add-mongosync-notes
gmiller-mdb Mar 24, 2025
411f10d
copy
gmiller-mdb Mar 24, 2025
77dcf50
move section
gmiller-mdb Mar 24, 2025
f5498c2
feedback
gmiller-mdb Mar 24, 2025
6412d48
nits
gmiller-mdb Mar 24, 2025
dd8e82f
feedback
gmiller-mdb Mar 25, 2025
6be3311
feedback
gmiller-mdb Mar 25, 2025
d6bb86e
add
gmiller-mdb Mar 27, 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
3 changes: 3 additions & 0 deletions source/reference/limitations.txt
View file
Open in desktop
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
11 changes: 11 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 @@ -179,6 +179,17 @@ 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`.

Embedded Config Server Shards
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a new term? I thought the term was just “config shard”.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@FGasper that was the language that the ticket used, I'll ask the person who created it before I publish!

Copy link
Contributor

Choose a reason for hiding this comment

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

@gmiller-mdb Example: https://www.mongodb.com/docs/manual/core/config-shard/

Copy link

@mvankeulen94 mvankeulen94 Mar 25, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

thank you, Felipe! I'm fine to change the language to Config Shard cluster and link to that page

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@mvankeulen94 just made the changes! would you mind taking a last look? thanks!

'''''''''''''''''''''''''''''

Starting in 8.0, MongoDB introduces support for embedded config server shards.

``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 embedded config sharded clusters.

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

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

Expand Down