@@ -359,23 +359,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
359
359
Pre-Split Chunks
360
360
~~~~~~~~~~~~~~~~
361
361
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.
371
366
372
367
.. _c2c-shard-replica-sets:
373
368
374
369
Shard Replica Sets
375
370
~~~~~~~~~~~~~~~~~~
376
371
377
- .. versionadded:: 1.1
378
-
379
372
Sync from a replica set to a sharded cluster requires the
380
373
``sharding`` option. This option configures how ``mongosync`` shards
381
374
collections.
@@ -386,8 +379,6 @@ Collections that are not listed in this array replicate as unsharded.
386
379
Supporting Indexes
387
380
~~~~~~~~~~~~~~~~~~
388
381
389
- .. versionadded:: 1.1
390
-
391
382
``mongosync`` syncs indexes from the source cluster to the destination
392
383
cluster. But, when syncing from a replica set to a sharded cluster,
393
384
``mongosync`` may require an additional index to support the shard key,
@@ -429,8 +420,6 @@ collections.
429
420
Rename During Sync
430
421
~~~~~~~~~~~~~~~~~~
431
422
432
- .. versionadded:: 1.1
433
-
434
423
Collections listed in the ``sharding.shardingEntries`` array
435
424
when synced from a replica set to a sharded cluster
436
425
become sharded collections on the destination cluster.
0 commit comments