Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

Commit 93f6f46

Browse files
committed
DOCSP-48525-disaster-recovery-faq-entry
1 parent d91d9a3 commit 93f6f46

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

source/faq.txt

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ Can I change the load level while ``mongosync`` is syncing?
2323
Yes, you can adjust the cluster workload level during a migration by
2424
following the steps in :ref:`c2c-reconfigure-mid-migration`.
2525

26+
.. _c2c-faq-reads-writes-mongosync:
27+
2628
Can I perform reads or writes to my destination cluster while ``mongosync`` is syncing?
2729
---------------------------------------------------------------------------------------
2830

@@ -232,4 +234,11 @@ Can I customize chunk distributions when syncing into a sharded cluster?
232234
No, you can't configure ``mongosync`` to customize chunk distributions
233235
on a destination sharded cluster. ``mongosync`` samples each collection
234236
during initialization to determine how to distribute documents
235-
efficiently across the destination cluster’s shards after migration.
237+
efficiently across the destination cluster’s shards after migration.
238+
239+
Can I use mongosync to set up a Disaster Recovery cluster?
240+
----------------------------------------------------------
241+
242+
This is not possible to do with ``mongosync`` today, since
243+
``mongosync`` must commit in order to safely accept traffic to the
244+
destination cluster. For more information, see :ref:`c2c-faq-reads-writes-mongosync`.

0 commit comments

Comments
 (0)