Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.
Merged
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
19 changes: 4 additions & 15 deletions source/reference/api/start.txt
Original file line number Diff line number Diff line change
Expand Up @@ -362,23 +362,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
Pre-Split Chunks
~~~~~~~~~~~~~~~~

.. versionadded:: 1.1

When ``mongosync`` syncs to a sharded cluster, it pre-splits chunks for
sharded collections on the destination cluster. This is supported in the
following configurations:

* Sync from a replica set to a sharded cluster.

* Sync between sharded clusters that differ in the number of shards.
When ``mongosync`` syncs to a sharded destination cluster, it pre-splits chunks
for sharded collections on the destination cluster. For each sharded collection,
``mongosync`` creates twice as many chunks as there are shards in the
destination cluster.

.. _c2c-shard-replica-sets:

Shard Replica Sets
~~~~~~~~~~~~~~~~~~

.. versionadded:: 1.1

Sync from a replica set to a sharded cluster requires the
``sharding`` option. This option configures how ``mongosync`` shards
collections.
Expand All @@ -391,8 +384,6 @@ Collections that are not listed in this array replicate as unsharded.
Supporting Indexes
~~~~~~~~~~~~~~~~~~

.. versionadded:: 1.1

``mongosync`` syncs indexes from the source cluster to the destination
cluster. But, when syncing from a replica set to a sharded cluster,
``mongosync`` may require an additional index to support the shard key,
Expand Down Expand Up @@ -434,8 +425,6 @@ collections.
Rename During Sync
~~~~~~~~~~~~~~~~~~

.. versionadded:: 1.1

Collections listed in the ``sharding.shardingEntries`` array
when synced from a replica set to a sharded cluster
become sharded collections on the destination cluster.
Expand Down