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

DOCSP-47159: Clarify write blocking recommendation on finalize cutover page #599

Merged
merged 7 commits into from
Feb 11, 2025
Merged

DOCSP-47159: Clarify write blocking recommendation on finalize cutover page #599

Changes from 4 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
6729e3c
init commit
mayaraman19 Feb 6, 2025
2ce91d9
rendering fix
mayaraman19 Feb 6, 2025
63abaa3
render
mayaraman19 Feb 6, 2025
894e725
clarity
mayaraman19 Feb 6, 2025
9f9dea9
change
mayaraman19 Feb 10, 2025
c3f320f
change
mayaraman19 Feb 10, 2025
2506068
remove link
mayaraman19 Feb 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion source/reference/cutover-process.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ Steps

For more information, see :ref:`c2c-verification`.

.. step:: Enable application writes on the destination cluster.
.. step:: If you did not start ``mongosync`` with :ref:`write-blocking <c2c-write-blocking>`, enable application writes on the destination cluster.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The user also only needs to do this step if they manually blocked writes on the dst. Could we update the step title to be something like "if you blocked writes on the destination cluster, enable application writes?" We can still keep the other note you added below


To enable writes, update :dbcommand:`setUserWriteBlockMode`:

Expand All @@ -179,6 +179,11 @@ Steps

Then, transfer your application workload to the destination cluster.

If you start ``mongosync``
with write-blocking by using the ``enableUserWriteBlocking`` option on
the :ref:`/start <c2c-api-start>` endpoint, you do not need
to complete this step.

.. step:: Call the ``progress`` endpoint to determine the status of the ``mongosync`` process.

When the ``mongosync`` progress response indicates that the
Expand Down