Skip to content

Commit ecd692a

Browse files
authored
DOCSP-30831 mongosync Commit Behavior Clarification (#188) (#199)
* DOCSP-30831 mongosync Commit Behavior Clarification * more explicit default behavior spec * copy * rebase
1 parent caf3d96 commit ecd692a

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

source/reference/mongosync.txt

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -217,17 +217,16 @@ Commit
217217
~~~~~~
218218

219219
To stop syncing, use the :ref:`commit <c2c-api-commit>` command on the
220-
destination cluster to convert indexes and finalize the changes. If you
221-
enable :ref:`write-blocking <c2c-write-blocking>`:
222-
220+
destination cluster to convert indexes and finalize the changes. By default,
221+
``commit`` operations have no effect on writes unless you enable
222+
:ref:`write-blocking <c2c-write-blocking>`. If you enable write blocking:
223223

224224
- ``commit`` blocks writes on the source cluster.
225225
- ``commit`` blocks writes on the destination cluster until
226226
``mongosync`` begins index validation.
227227

228-
229-
To monitor the ``commit`` process, use the :ref:`progress
230-
<c2c-api-progress>` command:
228+
The ``commit`` operation should take less than a few minutes. To monitor the
229+
``commit`` process, use the :ref:`progress <c2c-api-progress>` command:
231230

232231
- The destination cluster is writable when ``canWrite`` is true.
233232
- Index conversion is complete when ``mongosync`` enters the

0 commit comments

Comments
 (0)