From 6729e3c29fb51214b644e24787908d6fe84f9064 Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Thu, 6 Feb 2025 16:18:34 -0500 Subject: [PATCH 1/7] init commit --- source/reference/cutover-process.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index 0019daf41..239d0f7de 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -164,7 +164,9 @@ 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 `, + enable application writes on the destination cluster. To enable writes, update :dbcommand:`setUserWriteBlockMode`: @@ -179,6 +181,10 @@ Steps Then, transfer your application workload to the destination cluster. + You do not need to do this step if you start ``mongosync`` + with write-blocking using the ``enableUserWriteBlocking`` option when + you call the :ref:`/start ` API endpoint. + .. step:: Call the ``progress`` endpoint to determine the status of the ``mongosync`` process. When the ``mongosync`` progress response indicates that the From 2ce91d93ebe72d7809481682e7c29a2e6052d8c9 Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Thu, 6 Feb 2025 16:24:53 -0500 Subject: [PATCH 2/7] rendering fix --- source/reference/cutover-process.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index 239d0f7de..d93fc2629 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -165,8 +165,8 @@ Steps For more information, see :ref:`c2c-verification`. .. step:: If you did not start ``mongosync`` with - :ref:`write-blocking `, - enable application writes on the destination cluster. + :ref:`write-blocking `, + enable application writes on the destination cluster. To enable writes, update :dbcommand:`setUserWriteBlockMode`: From 63abaa376063a1c0cb07096435ae6b7163f1368c Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Thu, 6 Feb 2025 16:30:15 -0500 Subject: [PATCH 3/7] render --- source/reference/cutover-process.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index d93fc2629..cc2556ea2 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -164,9 +164,7 @@ Steps For more information, see :ref:`c2c-verification`. - .. step:: If you did not start ``mongosync`` with - :ref:`write-blocking `, - enable application writes on the destination cluster. + .. step:: If you did not start ``mongosync`` with :ref:`write-blocking `, enable application writes on the destination cluster. To enable writes, update :dbcommand:`setUserWriteBlockMode`: From 894e7256d64f118d9a7bcb98fe78323489bd9832 Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Thu, 6 Feb 2025 16:34:53 -0500 Subject: [PATCH 4/7] clarity --- source/reference/cutover-process.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index cc2556ea2..0de58749a 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -179,9 +179,10 @@ Steps Then, transfer your application workload to the destination cluster. - You do not need to do this step if you start ``mongosync`` - with write-blocking using the ``enableUserWriteBlocking`` option when - you call the :ref:`/start ` API endpoint. + If you start ``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. From 9f9dea9a1b7a4a37b3a0dbf9f327f815be6cc983 Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Mon, 10 Feb 2025 14:05:47 -0800 Subject: [PATCH 5/7] change --- source/reference/cutover-process.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index 0de58749a..9f97f88fe 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -164,7 +164,7 @@ Steps For more information, see :ref:`c2c-verification`. - .. step:: If you did not start ``mongosync`` with :ref:`write-blocking `, enable application writes on the destination cluster. + .. step:: If you manually :ref:`blocked writes ` on the destination cluster by using :dbcommand:`setUserWriteBlockMode`, enable application writes on the destination cluster. To enable writes, update :dbcommand:`setUserWriteBlockMode`: From c3f320fbef93aa9160afcf52680f086590611d7d Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Mon, 10 Feb 2025 14:11:09 -0800 Subject: [PATCH 6/7] change --- source/reference/cutover-process.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index 9f97f88fe..cfeb87162 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -179,7 +179,7 @@ Steps Then, transfer your application workload to the destination cluster. - If you start ``mongosync`` + 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. From 2506068d42017b4e39dbadfbc2c9d6ede87ed08a Mon Sep 17 00:00:00 2001 From: Maya Raman Date: Mon, 10 Feb 2025 14:22:59 -0800 Subject: [PATCH 7/7] remove link --- source/reference/cutover-process.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/reference/cutover-process.txt b/source/reference/cutover-process.txt index cfeb87162..60dbd70d4 100644 --- a/source/reference/cutover-process.txt +++ b/source/reference/cutover-process.txt @@ -164,7 +164,7 @@ Steps For more information, see :ref:`c2c-verification`. - .. step:: If you manually :ref:`blocked writes ` on the destination cluster by using :dbcommand:`setUserWriteBlockMode`, 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`: