From 1fc2bd307ec633fb33a85f7c90475b68f758a1d4 Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Tue, 18 Mar 2025 09:44:15 -0400 Subject: [PATCH 1/4] DOCSP-48421-clarify-verifier-lag-time --- source/includes/api/tables/progress-response.rst | 6 ++++++ source/reference/api/commit.txt | 7 ++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/source/includes/api/tables/progress-response.rst b/source/includes/api/tables/progress-response.rst index 777f0f1c9..4b154e3ac 100644 --- a/source/includes/api/tables/progress-response.rst +++ b/source/includes/api/tables/progress-response.rst @@ -53,6 +53,12 @@ writes on the source cluster. The time difference becomes zero when ``mongosync`` commits the migration. + With the introduction of the :ref:`embdedded verfier` + in version 1.9, there are now three different ``lagTimeSeconds`` fields: + - ``lagTimeSeconds`` for ``mongosync`` + - ``lagTimeSeconds`` for the source cluster for the verifier + - ``lagTimeSeconds`` for the destination cluster for the verifier + * - ``totalEventsApplied`` - integer - The approximate number of change events this instance of diff --git a/source/reference/api/commit.txt b/source/reference/api/commit.txt index ed7d0fc01..ed2b34fb5 100644 --- a/source/reference/api/commit.txt +++ b/source/reference/api/commit.txt @@ -36,7 +36,9 @@ Before using the ``commit`` endpoint: - Use the :ref:`progress ` endpoint to confirm the following values: - - ``lagTimeSeconds`` is near ``0`` (*Recommended, but not required*) + - ``lagTimeSeconds`` for ``mongosync``, the source cluster + for the verifier, and the destination cluster for the + verifier are all near ``0`` (*Recommended, but not required*) .. note:: lagTimeSeconds @@ -49,6 +51,9 @@ Before using the ``commit`` endpoint: When ``lagTimeSeconds`` is ``0``, the source and destination clusters are in a consistent state. + For more information on the ``lagTimeSeconds`` fields, see + :ref:`c2c-api-progress`. + - ``state: "RUNNING"`` - ``canCommit: true`` From e711fc33aab70d319e9861c9976ed5b055f14564 Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Tue, 18 Mar 2025 09:58:25 -0400 Subject: [PATCH 2/4] build error --- source/includes/api/tables/progress-response.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/includes/api/tables/progress-response.rst b/source/includes/api/tables/progress-response.rst index 4b154e3ac..74e4d5eef 100644 --- a/source/includes/api/tables/progress-response.rst +++ b/source/includes/api/tables/progress-response.rst @@ -55,9 +55,9 @@ With the introduction of the :ref:`embdedded verfier` in version 1.9, there are now three different ``lagTimeSeconds`` fields: - - ``lagTimeSeconds`` for ``mongosync`` - - ``lagTimeSeconds`` for the source cluster for the verifier - - ``lagTimeSeconds`` for the destination cluster for the verifier + - ``lagTimeSeconds`` for ``mongosync`` + - ``lagTimeSeconds`` for the source cluster for the verifier + - ``lagTimeSeconds`` for the destination cluster for the verifier * - ``totalEventsApplied`` - integer From dbe7fa1b88448ec91a8a5f28ae1a6aa87b78bcba Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Tue, 18 Mar 2025 10:39:33 -0400 Subject: [PATCH 3/4] reviewer update --- source/includes/api/tables/progress-response.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/includes/api/tables/progress-response.rst b/source/includes/api/tables/progress-response.rst index 74e4d5eef..284cc30ce 100644 --- a/source/includes/api/tables/progress-response.rst +++ b/source/includes/api/tables/progress-response.rst @@ -54,11 +54,15 @@ when ``mongosync`` commits the migration. With the introduction of the :ref:`embdedded verfier` - in version 1.9, there are now three different ``lagTimeSeconds`` fields: + in version 1.9, there are three different ``lagTimeSeconds`` fields whenever + embedded verification is enabled: - ``lagTimeSeconds`` for ``mongosync`` - ``lagTimeSeconds`` for the source cluster for the verifier - ``lagTimeSeconds`` for the destination cluster for the verifier + When embdedded verification is disabled, ``lagTimeSeconds`` only applies + to ``mongosync``. + * - ``totalEventsApplied`` - integer - The approximate number of change events this instance of From 15c71fe9d76e5a4d8d794204d103fe2166f519f0 Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Tue, 18 Mar 2025 17:41:17 -0400 Subject: [PATCH 4/4] fix render --- source/includes/api/tables/progress-response.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/source/includes/api/tables/progress-response.rst b/source/includes/api/tables/progress-response.rst index 284cc30ce..c3f3f03bf 100644 --- a/source/includes/api/tables/progress-response.rst +++ b/source/includes/api/tables/progress-response.rst @@ -56,6 +56,7 @@ With the introduction of the :ref:`embdedded verfier` in version 1.9, there are three different ``lagTimeSeconds`` fields whenever embedded verification is enabled: + - ``lagTimeSeconds`` for ``mongosync`` - ``lagTimeSeconds`` for the source cluster for the verifier - ``lagTimeSeconds`` for the destination cluster for the verifier