@@ -362,23 +362,16 @@ If the ``start`` request is successful, ``mongosync`` enters the
362
362
Pre-Split Chunks
363
363
~~~~~~~~~~~~~~~~
364
364
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.
374
369
375
370
.. _c2c-shard-replica-sets:
376
371
377
372
Shard Replica Sets
378
373
~~~~~~~~~~~~~~~~~~
379
374
380
- .. versionadded:: 1.1
381
-
382
375
Sync from a replica set to a sharded cluster requires the
383
376
``sharding`` option. This option configures how ``mongosync`` shards
384
377
collections.
@@ -391,8 +384,6 @@ Collections that are not listed in this array replicate as unsharded.
391
384
Supporting Indexes
392
385
~~~~~~~~~~~~~~~~~~
393
386
394
- .. versionadded:: 1.1
395
-
396
387
``mongosync`` syncs indexes from the source cluster to the destination
397
388
cluster. But, when syncing from a replica set to a sharded cluster,
398
389
``mongosync`` may require an additional index to support the shard key,
@@ -434,8 +425,6 @@ collections.
434
425
Rename During Sync
435
426
~~~~~~~~~~~~~~~~~~
436
427
437
- .. versionadded:: 1.1
438
-
439
428
Collections listed in the ``sharding.shardingEntries`` array
440
429
when synced from a replica set to a sharded cluster
441
430
become sharded collections on the destination cluster.
0 commit comments