@@ -17,6 +17,24 @@ This page provides answers to some frequently asked questions we have
17
17
encountered. If you have additional questions please contact MongoDB
18
18
Support.
19
19
20
+ Can I perform reads or writes to my destination cluster while ``mongosync`` is syncing?
21
+ ---------------------------------------------------------------------------------------
22
+
23
+ You can perform reads during synchronization if ``canCommit`` is ``true``.
24
+ However, the data that you read is
25
+ :term:`eventually consistent <eventual consistency>`, meaning that you might not
26
+ always read the latest writes.
27
+
28
+ During an ongoing sync, you can write to any non-synced namespaces in the
29
+ destination cluster as long as the source cluster doesn’t include a namespace
30
+ with the same name. If you write to a synced namespace before issuing a
31
+ :ref:`commit <c2c-api-commit>` and while ``canWrite`` is ``false``, the behavior
32
+ is undefined. To avoid this undefined behavior, you can enable
33
+ :ref:`write blocking <c2c-dr-write-blocking>`.
34
+
35
+ To check the value of ``canCommit`` or ``canWrite``, call the :ref:`progress
36
+ <c2c-api-progress>` API endpoint.
37
+
20
38
Can ``mongosync`` run on its own hardware?
21
39
------------------------------------------
22
40
@@ -116,7 +134,7 @@ source and destination clusters. If the clusters are underprovisioned for your
116
134
needs, consider upgrading the cluster hardware.
117
135
118
136
Should I stop a migration if the logs contain the word "error" or "failure"?
119
- --------------------------------------------------------------------------
137
+ ----------------------------------------------------------------------------
120
138
121
139
No, logs that contain the word "error" or "failure" show non-fatal
122
140
errors and do not signal that you need to stop ``mongosync`` early.
0 commit comments