@@ -359,23 +359,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
359359Pre-Split Chunks
360360~~~~~~~~~~~~~~~~
361361
362- .. versionadded:: 1.1
363-
364- When ``mongosync`` syncs to a sharded cluster, it pre-splits chunks for
365- sharded collections on the destination cluster. This is supported in the
366- following configurations:
367-
368- * Sync from a replica set to a sharded cluster.
369-
370- * Sync between sharded clusters that differ in the number of shards.
362+ When ``mongosync`` syncs to a sharded destination cluster, it pre-splits chunks
363+ for sharded collections on the destination cluster. For each sharded collection,
364+ ``mongosync`` creates twice as many chunks as there are shards in the
365+ destination cluster.
371366
372367.. _c2c-shard-replica-sets:
373368
374369Shard Replica Sets
375370~~~~~~~~~~~~~~~~~~
376371
377- .. versionadded:: 1.1
378-
379372Sync from a replica set to a sharded cluster requires the
380373``sharding`` option. This option configures how ``mongosync`` shards
381374collections.
@@ -386,8 +379,6 @@ Collections that are not listed in this array replicate as unsharded.
386379Supporting Indexes
387380~~~~~~~~~~~~~~~~~~
388381
389- .. versionadded:: 1.1
390-
391382``mongosync`` syncs indexes from the source cluster to the destination
392383cluster. But, when syncing from a replica set to a sharded cluster,
393384``mongosync`` may require an additional index to support the shard key,
@@ -429,8 +420,6 @@ collections.
429420Rename During Sync
430421~~~~~~~~~~~~~~~~~~
431422
432- .. versionadded:: 1.1
433-
434423Collections listed in the ``sharding.shardingEntries`` array
435424when synced from a replica set to a sharded cluster
436425become sharded collections on the destination cluster.
0 commit comments