@@ -352,23 +352,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
352352Pre-Split Chunks
353353~~~~~~~~~~~~~~~~
354354
355- .. versionadded:: 1.1
356-
357- When ``mongosync`` syncs to a sharded cluster, it pre-splits chunks for
358- sharded collections on the destination cluster. This is supported in the
359- following configurations:
360-
361- * Sync from a replica set to a sharded cluster.
362-
363- * Sync between sharded clusters that differ in the number of shards.
355+ When ``mongosync`` syncs to a sharded destination cluster, it pre-splits chunks
356+ for sharded collections on the destination cluster. For each sharded collection,
357+ ``mongosync`` creates twice as many chunks as there are shards in the
358+ destination cluster.
364359
365360.. _c2c-shard-replica-sets:
366361
367362Shard Replica Sets
368363~~~~~~~~~~~~~~~~~~
369364
370- .. versionadded:: 1.1
371-
372365Sync from a replica set to a sharded cluster requires the
373366``sharding`` option. This option configures how ``mongosync`` shards
374367collections.
@@ -381,8 +374,6 @@ Collections that are not listed in this array replicate as unsharded.
381374Supporting Indexes
382375~~~~~~~~~~~~~~~~~~
383376
384- .. versionadded:: 1.1
385-
386377``mongosync`` syncs indexes from the source cluster to the destination
387378cluster. But, when syncing from a replica set to a sharded cluster,
388379``mongosync`` may require an additional index to support the shard key,
@@ -424,8 +415,6 @@ collections.
424415Rename During Sync
425416~~~~~~~~~~~~~~~~~~
426417
427- .. versionadded:: 1.1
428-
429418Collections listed in the ``sharding.shardingEntries`` array
430419when synced from a replica set to a sharded cluster
431420become sharded collections on the destination cluster.
0 commit comments