From f47cca9ad4dc1a2ca8113c3ff51812ab50d4e369 Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Tue, 11 Feb 2025 06:41:16 -0800 Subject: [PATCH] DOCSP-47159: Clarify write blocking recommendation on finalize cutover page (#599) * init commit * rendering fix * render * clarity * change * change * remove link (cherry picked from commit 07991f7bb43b68d321f8f7af2b41d3052186d4d0) --- source/reference/cutover-process.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index 6f033e437..049f53e72 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -156,7 +156,7 @@ Steps For more information, see :ref:`c2c-verification`. - .. step:: Enable application writes on the destination cluster. + .. step:: If you manually blocked writes on the destination cluster by using :dbcommand:`setUserWriteBlockMode`, enable application writes on the destination cluster. To enable writes, update :dbcommand:`setUserWriteBlockMode`: @@ -171,6 +171,11 @@ Steps Then, transfer your application workload to the destination cluster. + If you started ``mongosync`` + with write-blocking by using the ``enableUserWriteBlocking`` option on + the :ref:`/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