From d28e1d8470a8a40be591b4edb39757f7efb88f7e Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Wed, 22 Jan 2025 12:03:28 -0500 Subject: [PATCH 1/4] DOCSP-46629-replSetResizeOplog-unsupported-Atlas --- source/reference/oplog-sizing.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/reference/oplog-sizing.txt b/source/reference/oplog-sizing.txt index 7d21f67bf..997342b4e 100644 --- a/source/reference/oplog-sizing.txt +++ b/source/reference/oplog-sizing.txt @@ -63,6 +63,12 @@ Monitor oplog Size Needed for Initial Sync - Increase the ``oplog`` window. Use :dbcommand:`replSetResizeOplog` to set ``minRetentionHours`` greater than the current ``oplog`` window. + + .. note:: + + :dbcommand:`replSetResizeOplog` is unsupported in Atlas. To resize + the oplog in Atlas, see :ref:`set-oplog-size`. + - Scale up the ``mongosync`` instance. Add CPU or memory to scale up the ``mongosync`` node so that it has a higher copy rate. From 23081372e62e7fd6b4e39e51138d871798e1120d Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Wed, 22 Jan 2025 14:28:05 -0500 Subject: [PATCH 2/4] indent --- source/reference/oplog-sizing.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/reference/oplog-sizing.txt b/source/reference/oplog-sizing.txt index 997342b4e..c3b0e437c 100644 --- a/source/reference/oplog-sizing.txt +++ b/source/reference/oplog-sizing.txt @@ -64,10 +64,10 @@ Monitor oplog Size Needed for Initial Sync to set ``minRetentionHours`` greater than the current ``oplog`` window. - .. note:: + .. note:: - :dbcommand:`replSetResizeOplog` is unsupported in Atlas. To resize - the oplog in Atlas, see :ref:`set-oplog-size`. + :dbcommand:`replSetResizeOplog` is unsupported in Atlas. To resize + the oplog in Atlas, see :ref:`set-oplog-size`. - Scale up the ``mongosync`` instance. Add CPU or memory to scale up the ``mongosync`` node so that it has a higher copy rate. From d166530de864287e147d98b14933c25f078d0f33 Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Thu, 23 Jan 2025 15:50:16 -0500 Subject: [PATCH 3/4] reviewer changes --- source/includes/fact-oplog-background.rst | 2 +- source/includes/fact-oplog-disk-storage.rst | 3 --- source/reference/oplog-sizing.txt | 2 +- 3 files changed, 2 insertions(+), 5 deletions(-) diff --git a/source/includes/fact-oplog-background.rst b/source/includes/fact-oplog-background.rst index b78a7876a..7869d7256 100644 --- a/source/includes/fact-oplog-background.rst +++ b/source/includes/fact-oplog-background.rst @@ -16,6 +16,6 @@ that is close to the real-time writes occurring on the source cluster. If you anticipate syncing a large data set, or if you plan to pause synchronization for an extended period of time, you might exceed the -:term:`oplog window`. Use the :setting:`~replication.oplogSizeMB` setting +:term:`oplog window`. Use the :setting:`~storage.oplogMinRetentionHours` setting to increase the size of the ``oplog`` on the source cluster. diff --git a/source/includes/fact-oplog-disk-storage.rst b/source/includes/fact-oplog-disk-storage.rst index 669f1755d..07cf94cfb 100644 --- a/source/includes/fact-oplog-disk-storage.rst +++ b/source/includes/fact-oplog-disk-storage.rst @@ -14,8 +14,5 @@ entries from the initial sync. If you need to reduce the overhead of the destination oplog entries and the embedded verifier is disabled, you can: -- Use the :setting:`~replication.oplogSizeMB` setting to lower the destination - cluster's oplog size. - - Use to :setting:`~storage.oplogMinRetentionHours` setting to lower or remove the destination cluster's minimum oplog retention period. \ No newline at end of file diff --git a/source/reference/oplog-sizing.txt b/source/reference/oplog-sizing.txt index c3b0e437c..98fa65ff6 100644 --- a/source/reference/oplog-sizing.txt +++ b/source/reference/oplog-sizing.txt @@ -67,7 +67,7 @@ Monitor oplog Size Needed for Initial Sync .. note:: :dbcommand:`replSetResizeOplog` is unsupported in Atlas. To resize - the oplog in Atlas, see :ref:`set-oplog-size`. + the oplog in Atlas, see :ref:`set-oplog-min-window`. - Scale up the ``mongosync`` instance. Add CPU or memory to scale up the ``mongosync`` node so that it has a higher copy rate. From bc61d51d308a182f106fcf268c66747303cd671a Mon Sep 17 00:00:00 2001 From: Anika Malhotra Date: Thu, 23 Jan 2025 15:55:06 -0500 Subject: [PATCH 4/4] undo some changes --- source/includes/fact-oplog-background.rst | 2 +- source/includes/fact-oplog-disk-storage.rst | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/source/includes/fact-oplog-background.rst b/source/includes/fact-oplog-background.rst index 7869d7256..b78a7876a 100644 --- a/source/includes/fact-oplog-background.rst +++ b/source/includes/fact-oplog-background.rst @@ -16,6 +16,6 @@ that is close to the real-time writes occurring on the source cluster. If you anticipate syncing a large data set, or if you plan to pause synchronization for an extended period of time, you might exceed the -:term:`oplog window`. Use the :setting:`~storage.oplogMinRetentionHours` setting +:term:`oplog window`. Use the :setting:`~replication.oplogSizeMB` setting to increase the size of the ``oplog`` on the source cluster. diff --git a/source/includes/fact-oplog-disk-storage.rst b/source/includes/fact-oplog-disk-storage.rst index 07cf94cfb..669f1755d 100644 --- a/source/includes/fact-oplog-disk-storage.rst +++ b/source/includes/fact-oplog-disk-storage.rst @@ -14,5 +14,8 @@ entries from the initial sync. If you need to reduce the overhead of the destination oplog entries and the embedded verifier is disabled, you can: +- Use the :setting:`~replication.oplogSizeMB` setting to lower the destination + cluster's oplog size. + - Use to :setting:`~storage.oplogMinRetentionHours` setting to lower or remove the destination cluster's minimum oplog retention period. \ No newline at end of file