@@ -26,20 +26,24 @@ following the steps in :ref:`c2c-reconfigure-mid-migration`.
26
26
Can I perform reads or writes to my destination cluster while ``mongosync`` is syncing?
27
27
---------------------------------------------------------------------------------------
28
28
29
- You can perform reads at any time during synchronization.
30
- However, ``mongosync`` combines and reorders writes from the source to destination during synchronization,
31
- and also temporarily modifies various collection characteristics.
32
- As a result, the destination is not guaranteed to match the source at any point in time when the sync is running.
33
- For consistent reads, wait for the migration to :ref:`c2c-api-commit`. To learn more, see :ref:`mongosync-considerations`.
34
-
35
- Performing writes to your destination cluster during synchronization results in undefined behavior.
36
- ``mongosync`` blocks writes on the destination cluster by default. To learn
37
- more about write-blocking, see :ref:`c2c-write-blocking` and :ref:`c2c-api-start`.
38
-
39
- Upon commit, it is only safe to write to the destination cluster when ``canWrite`` is ``true``.
40
- To check the value of ``canWrite``, run the :ref:`c2c-api-progress` endpoint.
41
-
42
- To learn more about permissable reads and writes during synchronization, see :ref:`c2c-reads-and-writes`.
29
+ ``mongosync`` combines and reorders writes from the source to destination during
30
+ synchronization, and temporarily modifies various collection characteristics.
31
+ As a result, the destination is not guaranteed to match the source, including a
32
+ stale version of the source, at any point in time when the sync is running. To
33
+ safely accept traffic to the destination cluster, wait for the migration to
34
+ :ref:`c2c-api-commit`. To learn more, see :ref:`mongosync-considerations`.
35
+
36
+ Performing writes to your destination cluster during synchronization results in
37
+ undefined behavior. ``mongosync`` blocks writes on the destination cluster by
38
+ default. To learn more about write-blocking, see :ref:`c2c-write-blocking` and
39
+ :ref:`c2c-api-start`.
40
+
41
+ Upon commit, it is only safe to write to the destination cluster when
42
+ ``canWrite`` is ``true``. To check the value of ``canWrite``, run the
43
+ :ref:`c2c-api-progress` endpoint.
44
+
45
+ To learn more about permissable reads and writes during synchronization, see
46
+ :ref:`c2c-reads-and-writes`.
43
47
44
48
.. note::
45
49
0 commit comments