From 692ca4eae0694f5673ce896a640cb3e07b6be8cd Mon Sep 17 00:00:00 2001 From: Alison Huh Date: Thu, 14 Nov 2024 14:47:28 -0500 Subject: [PATCH 1/4] DOCSP-44478-hardware-specs --- source/faq.txt | 22 +++++++++++++++++++++ source/includes/fact-oplog-disk-storage.rst | 7 +++++++ source/includes/fact-oplog-reduction.rst | 7 +++++++ source/quickstart.txt | 2 ++ source/reference/oplog-sizing.txt | 5 +++++ 5 files changed, 43 insertions(+) create mode 100644 source/includes/fact-oplog-disk-storage.rst create mode 100644 source/includes/fact-oplog-reduction.rst diff --git a/source/faq.txt b/source/faq.txt index ad7fae829..0d57d7346 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -47,6 +47,28 @@ have to run on the servers that host your MongoDB instances. When (OS) that is different than the OS on the source or destination clusters. +What hardware specifications should the destination cluster have? +----------------------------------------------------------------- + +For most migrations, the destination cluster should have higher hardware +specifications than the source cluster, including the following properties: + +- CPU +- Memory +- Disk I/O + +These hardware specifications ensure that the destination cluster can handle +``mongosync`` writes and that the sync can keep up with the source cluster's +workload. + +Additionally, the destination cluster must have enough disk storage to +accommodate the logical data size being migrated and the destination oplog +entries from the initial sync. For example, to migrate 10 GB of data, the +destination cluster should have at least 10 GB available for the data +and another 10 GB for the insert oplog entries. + +.. include:: /includes/fact-oplog-reduction.rst + .. _c2c-faq-increase-oplog: Should I increase the size of the ``oplog`` in the source cluster? diff --git a/source/includes/fact-oplog-disk-storage.rst b/source/includes/fact-oplog-disk-storage.rst new file mode 100644 index 000000000..1ce1d773c --- /dev/null +++ b/source/includes/fact-oplog-disk-storage.rst @@ -0,0 +1,7 @@ +The destination cluster must have enough disk storage to accommodate the logical +data size being migrated and the destination oplog entries from the initial +sync. For example, to migrate 10 GB of data, the destination cluster must have +at least 10 GB available for the data and another 10 GB for the insert oplog +entries. + +.. include:: /includes/fact-oplog-reduction.rst diff --git a/source/includes/fact-oplog-reduction.rst b/source/includes/fact-oplog-reduction.rst new file mode 100644 index 000000000..c77d8a8fb --- /dev/null +++ b/source/includes/fact-oplog-reduction.rst @@ -0,0 +1,7 @@ +To reduce the overhead of the destination oplog entries, 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/quickstart.txt b/source/quickstart.txt index 9950c3500..20ebdee7e 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -80,6 +80,8 @@ Setup The number of nodes in the destination replica set does not have to equal the number of nodes in the source replica set. + .. include:: /includes/fact-oplog-disk-storage.rst + If your clusters are self-managed, they must be MongoDB Enterprise clusters. {+c2c-product-name+} is only supported on MongoDB Community Edition in a limited number of cases. For more diff --git a/source/reference/oplog-sizing.txt b/source/reference/oplog-sizing.txt index 3dd86f041..7d21f67bf 100644 --- a/source/reference/oplog-sizing.txt +++ b/source/reference/oplog-sizing.txt @@ -20,6 +20,11 @@ be within the ``oplog`` time range. .. include:: /includes/fact-oplog-background +Considerations +-------------- + +.. include:: /includes/fact-oplog-disk-storage.rst + Monitor oplog Size Needed for Initial Sync ------------------------------------------ From 1b434509c1897a8a68b4172cbccfc0cee4511a80 Mon Sep 17 00:00:00 2001 From: Alison Huh Date: Thu, 14 Nov 2024 15:42:17 -0500 Subject: [PATCH 2/4] important note --- source/quickstart.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index 20ebdee7e..1816e2f0f 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -80,7 +80,9 @@ Setup The number of nodes in the destination replica set does not have to equal the number of nodes in the source replica set. - .. include:: /includes/fact-oplog-disk-storage.rst + .. important:: + + .. include:: /includes/fact-oplog-disk-storage.rst If your clusters are self-managed, they must be MongoDB Enterprise clusters. {+c2c-product-name+} is only supported on From e7744e025face9b15f4c2420673ea326ae5e094f Mon Sep 17 00:00:00 2001 From: Alison Huh Date: Fri, 15 Nov 2024 11:21:14 -0500 Subject: [PATCH 3/4] JD feedback --- source/faq.txt | 8 +------- source/includes/fact-oplog-disk-storage.rst | 8 +++++++- source/includes/fact-oplog-reduction.rst | 7 ------- 3 files changed, 8 insertions(+), 15 deletions(-) delete mode 100644 source/includes/fact-oplog-reduction.rst diff --git a/source/faq.txt b/source/faq.txt index 0d57d7346..7d46c80b6 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -61,13 +61,7 @@ These hardware specifications ensure that the destination cluster can handle ``mongosync`` writes and that the sync can keep up with the source cluster's workload. -Additionally, the destination cluster must have enough disk storage to -accommodate the logical data size being migrated and the destination oplog -entries from the initial sync. For example, to migrate 10 GB of data, the -destination cluster should have at least 10 GB available for the data -and another 10 GB for the insert oplog entries. - -.. include:: /includes/fact-oplog-reduction.rst +.. include:: /includes/fact-oplog-disk-storage.rst .. _c2c-faq-increase-oplog: diff --git a/source/includes/fact-oplog-disk-storage.rst b/source/includes/fact-oplog-disk-storage.rst index 1ce1d773c..8571e8e2d 100644 --- a/source/includes/fact-oplog-disk-storage.rst +++ b/source/includes/fact-oplog-disk-storage.rst @@ -4,4 +4,10 @@ sync. For example, to migrate 10 GB of data, the destination cluster must have at least 10 GB available for the data and another 10 GB for the insert oplog entries. -.. include:: /includes/fact-oplog-reduction.rst +To reduce the overhead of the destination oplog entries, 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. diff --git a/source/includes/fact-oplog-reduction.rst b/source/includes/fact-oplog-reduction.rst deleted file mode 100644 index c77d8a8fb..000000000 --- a/source/includes/fact-oplog-reduction.rst +++ /dev/null @@ -1,7 +0,0 @@ -To reduce the overhead of the destination oplog entries, 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 From 99821cc2fc6d706f83fb4e99d7789f09c51cd8e5 Mon Sep 17 00:00:00 2001 From: Alison Huh Date: Fri, 15 Nov 2024 14:55:00 -0500 Subject: [PATCH 4/4] ED feedback --- source/includes/fact-oplog-disk-storage.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/includes/fact-oplog-disk-storage.rst b/source/includes/fact-oplog-disk-storage.rst index 8571e8e2d..5df36ed35 100644 --- a/source/includes/fact-oplog-disk-storage.rst +++ b/source/includes/fact-oplog-disk-storage.rst @@ -2,12 +2,12 @@ The destination cluster must have enough disk storage to accommodate the logical data size being migrated and the destination oplog entries from the initial sync. For example, to migrate 10 GB of data, the destination cluster must have at least 10 GB available for the data and another 10 GB for the insert oplog -entries. +entries from the initial sync. To reduce the overhead of the destination oplog entries, you can: - Use the :setting:`~replication.oplogSizeMB` setting to lower the destination - cluster's oplog size + cluster's oplog size. - Use to :setting:`~storage.oplogMinRetentionHours` setting to lower or remove the destination cluster's minimum oplog retention period.