@@ -362,23 +362,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
362362Pre-Split Chunks
363363~~~~~~~~~~~~~~~~
364364
365- .. versionadded:: 1.1
366-
367- When ``mongosync`` syncs to a sharded cluster, it pre-splits chunks for
368- sharded collections on the destination cluster. This is supported in the
369- following configurations:
370-
371- * Sync from a replica set to a sharded cluster.
372-
373- * Sync between sharded clusters that differ in the number of shards.
365+ When ``mongosync`` syncs to a sharded destination cluster, it pre-splits chunks
366+ for sharded collections on the destination cluster. For each sharded collection,
367+ ``mongosync`` creates twice as many chunks as there are shards in the
368+ destination cluster.
374369
375370.. _c2c-shard-replica-sets:
376371
377372Shard Replica Sets
378373~~~~~~~~~~~~~~~~~~
379374
380- .. versionadded:: 1.1
381-
382375Sync from a replica set to a sharded cluster requires the
383376``sharding`` option. This option configures how ``mongosync`` shards
384377collections.
@@ -391,8 +384,6 @@ Collections that are not listed in this array replicate as unsharded.
391384Supporting Indexes
392385~~~~~~~~~~~~~~~~~~
393386
394- .. versionadded:: 1.1
395-
396387``mongosync`` syncs indexes from the source cluster to the destination
397388cluster. But, when syncing from a replica set to a sharded cluster,
398389``mongosync`` may require an additional index to support the shard key,
@@ -434,8 +425,6 @@ collections.
434425Rename During Sync
435426~~~~~~~~~~~~~~~~~~
436427
437- .. versionadded:: 1.1
438-
439428Collections listed in the ``sharding.shardingEntries`` array
440429when synced from a replica set to a sharded cluster
441430become sharded collections on the destination cluster.
0 commit comments