From d7b60e75bf978e3312dbd3493338e4b49a6ddf82 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Mon, 18 Sep 2023 11:48:21 -0700 Subject: [PATCH 01/38] DOCSP-29504-many-to-one-clusters --- source/release-notes/1.7.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 2c61b3ca8..1fa106939 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -101,6 +101,7 @@ Issues Fixed: 1.7.0 Release ------------- +<<<<<<< HEAD **October 18, 2023** Live Upgrade From 9ee0798187ed742a59e184ac3998a60e1faf2a93 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Mon, 18 Sep 2023 12:34:33 -0700 Subject: [PATCH 02/38] DOCSP-29504-many-to-one-clusters --- source/release-notes/1.7.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 1fa106939..2c61b3ca8 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -101,7 +101,6 @@ Issues Fixed: 1.7.0 Release ------------- -<<<<<<< HEAD **October 18, 2023** Live Upgrade From 4eacfcbd6ba322554ece58f485a55d3142916516 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Mon, 18 Sep 2023 12:49:56 -0700 Subject: [PATCH 03/38] DOCSP-29504-many-to-one-clusters --- source/includes/one-to-many-cluster-sync.rst | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 source/includes/one-to-many-cluster-sync.rst diff --git a/source/includes/one-to-many-cluster-sync.rst b/source/includes/one-to-many-cluster-sync.rst new file mode 100644 index 000000000..8cf8094e3 --- /dev/null +++ b/source/includes/one-to-many-cluster-sync.rst @@ -0,0 +1,2 @@ +Starting in 1.7.0, ``mongosync`` can send data from one to many +clusters. \ No newline at end of file From e75c5c1bda85a0959c9b49e06cff3c8d2a818785 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Mon, 18 Sep 2023 15:03:11 -0700 Subject: [PATCH 04/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-to-one-cluster-sync.rst | 9 +++++++++ source/includes/migrationName-description.rst | 7 +++++++ source/includes/one-to-many-cluster-sync.rst | 2 -- source/release-notes/1.7.txt | 5 +++++ 4 files changed, 21 insertions(+), 2 deletions(-) create mode 100644 source/includes/many-to-one-cluster-sync.rst create mode 100644 source/includes/migrationName-description.rst delete mode 100644 source/includes/one-to-many-cluster-sync.rst diff --git a/source/includes/many-to-one-cluster-sync.rst b/source/includes/many-to-one-cluster-sync.rst new file mode 100644 index 000000000..ee6009ba2 --- /dev/null +++ b/source/includes/many-to-one-cluster-sync.rst @@ -0,0 +1,9 @@ +Starting in 1.7.0, ``mongosync`` can migrate data from many clusters to +the same cluster. + +You can also set a name for a data migration. For example, you +can set a migration name to differentiate multiple migrations that send +data to the same destination cluster. For details, see: + +- :setting:`migrationName` configuration file setting +- :option:`migrationName` command line option diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst new file mode 100644 index 000000000..c3fc1e9bc --- /dev/null +++ b/source/includes/migrationName-description.rst @@ -0,0 +1,7 @@ +Starting in 1.7.0, you can set a name for a data migration. For example, +you can set a migration name to differentiate multiple migrations that +send data to the same destination cluster. To set a data migration name, +see: + +- :setting:`migrationName` configuration file setting +- :option:`migrationName` command line option diff --git a/source/includes/one-to-many-cluster-sync.rst b/source/includes/one-to-many-cluster-sync.rst deleted file mode 100644 index 8cf8094e3..000000000 --- a/source/includes/one-to-many-cluster-sync.rst +++ /dev/null @@ -1,2 +0,0 @@ -Starting in 1.7.0, ``mongosync`` can send data from one to many -clusters. \ No newline at end of file diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 2c61b3ca8..5b49a2462 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -136,6 +136,11 @@ Issues Fixed: initialization if the user specified only an exclusion filter and there were no fully excluded databases. +Set a Migration Name +~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/migrationName-description.rst + Minimum Supported Version ------------------------- From b9f7fb074613537785182680ad25221601e99389 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Mon, 18 Sep 2023 17:02:18 -0700 Subject: [PATCH 05/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-to-one-cluster-sync.rst | 9 +-------- source/includes/migrationName-description.rst | 6 +----- source/includes/migrationName.rst | 14 ++++++++++++++ source/release-notes/1.7.txt | 5 +++++ 4 files changed, 21 insertions(+), 13 deletions(-) create mode 100644 source/includes/migrationName.rst diff --git a/source/includes/many-to-one-cluster-sync.rst b/source/includes/many-to-one-cluster-sync.rst index ee6009ba2..92645d5e9 100644 --- a/source/includes/many-to-one-cluster-sync.rst +++ b/source/includes/many-to-one-cluster-sync.rst @@ -1,9 +1,2 @@ Starting in 1.7.0, ``mongosync`` can migrate data from many clusters to -the same cluster. - -You can also set a name for a data migration. For example, you -can set a migration name to differentiate multiple migrations that send -data to the same destination cluster. For details, see: - -- :setting:`migrationName` configuration file setting -- :option:`migrationName` command line option +one cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index c3fc1e9bc..65c10d799 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,7 +1,3 @@ Starting in 1.7.0, you can set a name for a data migration. For example, you can set a migration name to differentiate multiple migrations that -send data to the same destination cluster. To set a data migration name, -see: - -- :setting:`migrationName` configuration file setting -- :option:`migrationName` command line option +send data to the same destination cluster. diff --git a/source/includes/migrationName.rst b/source/includes/migrationName.rst new file mode 100644 index 000000000..ed06271a9 --- /dev/null +++ b/source/includes/migrationName.rst @@ -0,0 +1,14 @@ +.. reference/configuration.txt +.. reference/mongosync.txt + +.. versionadded:: 1.7.0 + +.. include:: /includes/migrationName-description.rst + +The ``migrationName`` string can contain a maximum of 44 alphanumeric or +underscore characters. ``migrationName`` is appended to the string +``"mongosync_internal_"``. + +For example, if you set ``migrationName`` to ``"Clusters 3 through 17 to +cluster 20"``, the string added to the database is +``"mongosync_internal_Clusters 3 through 17 to cluster 20"`` diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 5b49a2462..65c99d088 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -141,6 +141,11 @@ Set a Migration Name .. include:: /includes/migrationName-description.rst +To set a data migration name, see: + +- :setting:`migrationName` configuration file setting +- :option:`migrationName` command line option + Minimum Supported Version ------------------------- From 0312da926d802df983cc94d73084b2303c833366 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 10:43:59 -0700 Subject: [PATCH 06/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-to-one-cluster-sync.rst | 4 +++- source/includes/migrationName.rst | 19 ++++++++++++++++--- source/quickstart.txt | 12 ++++++++++++ 3 files changed, 31 insertions(+), 4 deletions(-) diff --git a/source/includes/many-to-one-cluster-sync.rst b/source/includes/many-to-one-cluster-sync.rst index 92645d5e9..bbb8a9727 100644 --- a/source/includes/many-to-one-cluster-sync.rst +++ b/source/includes/many-to-one-cluster-sync.rst @@ -1,2 +1,4 @@ Starting in 1.7.0, ``mongosync`` can migrate data from many clusters to -one cluster. +one cluster. This allows you to consolidate data from small clusters +into a centralized cluster, migrate data to a cluster with +existing data, and other benefits. diff --git a/source/includes/migrationName.rst b/source/includes/migrationName.rst index ed06271a9..75b737081 100644 --- a/source/includes/migrationName.rst +++ b/source/includes/migrationName.rst @@ -9,6 +9,19 @@ The ``migrationName`` string can contain a maximum of 44 alphanumeric or underscore characters. ``migrationName`` is appended to the string ``"mongosync_internal_"``. -For example, if you set ``migrationName`` to ``"Clusters 3 through 17 to -cluster 20"``, the string added to the database is -``"mongosync_internal_Clusters 3 through 17 to cluster 20"`` +For example, if you set ``migrationName`` to ``"Cluster 27000 to +cluster 35000"``, the string added to the database is +``"mongosync_internal_Cluster 27000 to cluster 35000"``. + +For a many-to-one cluster migration, you could set the migration names +on the command line as shown in this example scenario: + +.. code-block:: shell + + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27000" \ + --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27000 to cluster 35000" + + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27001" \ + --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27001 to cluster 35000" diff --git a/source/quickstart.txt b/source/quickstart.txt index 2483c123f..331c0f900 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -33,6 +33,9 @@ the rest of the {+c2c-product-name+} documentation. - Sharded clusters are not required to have the same number of shards. +{+c2c-product-name+} syncs data between clusters. To run +``mongosync``, you will need to: + - The destination cluster must be the same version or up to two versions ahead of the source cluster. The patch version is not important, so long as they meets the minimum patch :ref:`version requirements @@ -305,3 +308,12 @@ Synchronization Notes - To estimate the size of ``oplog`` needed for initial synchronization, see :ref:`c2c-oplog-sizing`. +<<<<<<< HEAD +======= + +Synchronize Data from Many Clusters to One Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/many-to-one-cluster-sync.rst + +>>>>>>> b2a0473... DOCSP-29504-many-to-one-clusters From 7b0c9cf91d8586888c56343cc775e1b2b17781c4 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 10:52:43 -0700 Subject: [PATCH 07/38] DOCSP-29504-many-to-one-clusters --- source/index.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/index.txt b/source/index.txt index 90fc25181..3e50046e6 100644 --- a/source/index.txt +++ b/source/index.txt @@ -9,7 +9,7 @@ Cluster-to-Cluster Sync .. default-domain:: mongodb {+c2c-product-name+} provides continuous data synchronization or a -one-time data migration between two MongoDB clusters. You can enable +one-time data migration between MongoDB clusters. You can enable {+c2c-product-name+} with the :ref:`mongosync ` utility. ``mongosync`` can continuously synchronize data between two clusters. From 2bb9bf88310413d16d046d1fd0d832938c697968 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 14:33:00 -0700 Subject: [PATCH 08/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-to-one-cluster-sync.rst | 4 --- source/includes/many-to-one-cluster.rst | 3 ++ source/includes/migrationName-description.rst | 4 +-- source/includes/migrationName.rst | 13 +------- source/quickstart.txt | 30 +++++++++++++++++-- source/release-notes/1.7.txt | 2 +- 6 files changed, 34 insertions(+), 22 deletions(-) delete mode 100644 source/includes/many-to-one-cluster-sync.rst create mode 100644 source/includes/many-to-one-cluster.rst diff --git a/source/includes/many-to-one-cluster-sync.rst b/source/includes/many-to-one-cluster-sync.rst deleted file mode 100644 index bbb8a9727..000000000 --- a/source/includes/many-to-one-cluster-sync.rst +++ /dev/null @@ -1,4 +0,0 @@ -Starting in 1.7.0, ``mongosync`` can migrate data from many clusters to -one cluster. This allows you to consolidate data from small clusters -into a centralized cluster, migrate data to a cluster with -existing data, and other benefits. diff --git a/source/includes/many-to-one-cluster.rst b/source/includes/many-to-one-cluster.rst new file mode 100644 index 000000000..36897e7c1 --- /dev/null +++ b/source/includes/many-to-one-cluster.rst @@ -0,0 +1,3 @@ +Starting in 1.7.0, ``mongosync`` can sync data from many clusters +to one cluster. For example, you can consolidate data from many small +clusters to one centralized cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index 65c10d799..1364351b2 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,3 +1,3 @@ Starting in 1.7.0, you can set a name for a data migration. For example, -you can set a migration name to differentiate multiple migrations that -send data to the same destination cluster. +you can set a migration name to differentiate the operations from many +clusters to one cluster. diff --git a/source/includes/migrationName.rst b/source/includes/migrationName.rst index 75b737081..60c3b0a7f 100644 --- a/source/includes/migrationName.rst +++ b/source/includes/migrationName.rst @@ -13,15 +13,4 @@ For example, if you set ``migrationName`` to ``"Cluster 27000 to cluster 35000"``, the string added to the database is ``"mongosync_internal_Cluster 27000 to cluster 35000"``. -For a many-to-one cluster migration, you could set the migration names -on the command line as shown in this example scenario: - -.. code-block:: shell - - ./bin/mongosync \ - --cluster0 "mongodb://localhost:27000" \ - --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27000 to cluster 35000" - - ./bin/mongosync \ - --cluster0 "mongodb://localhost:27001" \ - --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27001 to cluster 35000" +For a full example, see :ref:`c2c-quickstart-many-to-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index 331c0f900..28daf979b 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -198,6 +198,8 @@ Initialization Notes ` command. "cluster0" and "cluster1" are just labels, either cluster can be ``cluster0`` or ``cluster1``. +.. _c2c-quickstart-synchronize: + Synchronize Data Between Clusters --------------------------------- @@ -311,9 +313,31 @@ Synchronization Notes <<<<<<< HEAD ======= -Synchronize Data from Many Clusters to One Cluster -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. _c2c-quickstart-many-to-one: + +Sync Data from Many Clusters to One Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/many-to-one-cluster.rst + +The following examples show two commands that connect to the +clusters running on port 27000 and 27001 to the cluster running on port +35000. The commands also set the optional :option:`migrationName` +command line option to differentiate the operations. -.. include:: /includes/many-to-one-cluster-sync.rst +.. code-block:: shell + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27000" \ + --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27000 to cluster 35000" + + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27001" \ + --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27001 to cluster 35000" + +<<<<<<< HEAD >>>>>>> b2a0473... DOCSP-29504-many-to-one-clusters +======= +You can then start the data sync from the two clusters to the one +cluster. For details, see :ref:`c2c-quickstart-synchronize`. +>>>>>>> 9323628... DOCSP-29504-many-to-one-clusters diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 65c99d088..201e06cba 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -141,7 +141,7 @@ Set a Migration Name .. include:: /includes/migrationName-description.rst -To set a data migration name, see: +To set a migration name, see: - :setting:`migrationName` configuration file setting - :option:`migrationName` command line option From d28ec9fd426c792270b1b8440828c5f9919ca3e9 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 15:51:24 -0700 Subject: [PATCH 09/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-to-one-cluster.rst | 3 --- source/includes/many-with-one-cluster.rst | 3 +++ source/includes/migrationName-description.rst | 2 +- source/includes/migrationName.rst | 2 +- source/quickstart.txt | 27 +++++++++++++------ source/reference/limitations.txt | 1 - 6 files changed, 24 insertions(+), 14 deletions(-) delete mode 100644 source/includes/many-to-one-cluster.rst create mode 100644 source/includes/many-with-one-cluster.rst diff --git a/source/includes/many-to-one-cluster.rst b/source/includes/many-to-one-cluster.rst deleted file mode 100644 index 36897e7c1..000000000 --- a/source/includes/many-to-one-cluster.rst +++ /dev/null @@ -1,3 +0,0 @@ -Starting in 1.7.0, ``mongosync`` can sync data from many clusters -to one cluster. For example, you can consolidate data from many small -clusters to one centralized cluster. diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst new file mode 100644 index 000000000..b9cb00b19 --- /dev/null +++ b/source/includes/many-with-one-cluster.rst @@ -0,0 +1,3 @@ +Starting in 1.7.0, ``mongosync`` can sync many source clusters with one +destination cluster. For example, you can consolidate data from many +small clusters with one centralized cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index 1364351b2..a11e9f829 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,3 +1,3 @@ Starting in 1.7.0, you can set a name for a data migration. For example, you can set a migration name to differentiate the operations from many -clusters to one cluster. +clusters with one cluster. diff --git a/source/includes/migrationName.rst b/source/includes/migrationName.rst index 60c3b0a7f..0b0224f2a 100644 --- a/source/includes/migrationName.rst +++ b/source/includes/migrationName.rst @@ -13,4 +13,4 @@ For example, if you set ``migrationName`` to ``"Cluster 27000 to cluster 35000"``, the string added to the database is ``"mongosync_internal_Cluster 27000 to cluster 35000"``. -For a full example, see :ref:`c2c-quickstart-many-to-one`. +For a full example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index 28daf979b..8bbf949f6 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -313,17 +313,18 @@ Synchronization Notes <<<<<<< HEAD ======= -.. _c2c-quickstart-many-to-one: +.. _c2c-quickstart-many-with-one: -Sync Data from Many Clusters to One Cluster -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Sync Many Source Clusters with One Destination Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. include:: /includes/many-to-one-cluster.rst +.. include:: /includes/many-with-one-cluster.rst -The following examples show two commands that connect to the -clusters running on port 27000 and 27001 to the cluster running on port -35000. The commands also set the optional :option:`migrationName` -command line option to differentiate the operations. +The following examples show two commands that connect the source +clusters running on port 27000 and 27001 with the destination cluster +running on port 35000. The commands also set the optional +:option:`migrationName` command line option to differentiate the +operations. .. code-block:: shell @@ -335,9 +336,19 @@ command line option to differentiate the operations. --cluster0 "mongodb://localhost:27001" \ --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27001 to cluster 35000" +<<<<<<< HEAD <<<<<<< HEAD >>>>>>> b2a0473... DOCSP-29504-many-to-one-clusters ======= You can then start the data sync from the two clusters to the one cluster. For details, see :ref:`c2c-quickstart-synchronize`. >>>>>>> 9323628... DOCSP-29504-many-to-one-clusters +======= +You can then start the sync between the two source clusters and the +destination cluster. For details, see the earlier section +:ref:`c2c-quickstart-synchronize`. + +.. note:: + + All the clusters must have unique database and collection namespaces. +>>>>>>> e847913... DOCSP-29504-many-to-one-clusters diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 2e0b3ae93..4be1bc201 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -55,7 +55,6 @@ General Limitations - ``mongosync`` must read from the source cluster using the :readmode:`primary` read preference. - MongoDB Community Edition ------------------------- From a198bf3249713f17c342a75f16c4ffcca35ad275 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 16:05:10 -0700 Subject: [PATCH 10/38] DOCSP-29504-many-to-one-clusters --- source/includes/migrationName-description.rst | 4 +- source/quickstart.txt | 48 ++----------------- 2 files changed, 5 insertions(+), 47 deletions(-) diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index a11e9f829..6ec684ab8 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,3 +1,3 @@ Starting in 1.7.0, you can set a name for a data migration. For example, -you can set a migration name to differentiate the operations from many -clusters with one cluster. +you can set a migration name to identify the sync operations from many +source clusters with one destination cluster. diff --git a/source/quickstart.txt b/source/quickstart.txt index 8bbf949f6..7b8bb3d1f 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -33,9 +33,6 @@ the rest of the {+c2c-product-name+} documentation. - Sharded clusters are not required to have the same number of shards. -{+c2c-product-name+} syncs data between clusters. To run -``mongosync``, you will need to: - - The destination cluster must be the same version or up to two versions ahead of the source cluster. The patch version is not important, so long as they meets the minimum patch :ref:`version requirements @@ -198,8 +195,6 @@ Initialization Notes ` command. "cluster0" and "cluster1" are just labels, either cluster can be ``cluster0`` or ``cluster1``. -.. _c2c-quickstart-synchronize: - Synchronize Data Between Clusters --------------------------------- @@ -310,45 +305,8 @@ Synchronization Notes - To estimate the size of ``oplog`` needed for initial synchronization, see :ref:`c2c-oplog-sizing`. -<<<<<<< HEAD -======= - -.. _c2c-quickstart-many-with-one: - -Sync Many Source Clusters with One Destination Cluster -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -.. include:: /includes/many-with-one-cluster.rst - -The following examples show two commands that connect the source -clusters running on port 27000 and 27001 with the destination cluster -running on port 35000. The commands also set the optional -:option:`migrationName` command line option to differentiate the -operations. - -.. code-block:: shell - - ./bin/mongosync \ - --cluster0 "mongodb://localhost:27000" \ - --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27000 to cluster 35000" - - ./bin/mongosync \ - --cluster0 "mongodb://localhost:27001" \ - --cluster1 "mongodb://localhost:35000" --migrationName "Cluster 27001 to cluster 35000" - -<<<<<<< HEAD -<<<<<<< HEAD ->>>>>>> b2a0473... DOCSP-29504-many-to-one-clusters -======= -You can then start the data sync from the two clusters to the one -cluster. For details, see :ref:`c2c-quickstart-synchronize`. ->>>>>>> 9323628... DOCSP-29504-many-to-one-clusters -======= -You can then start the sync between the two source clusters and the -destination cluster. For details, see the earlier section -:ref:`c2c-quickstart-synchronize`. -.. note:: +Synchronize Data from Many Clusters to One Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - All the clusters must have unique database and collection namespaces. ->>>>>>> e847913... DOCSP-29504-many-to-one-clusters +.. include:: /includes/many-to-one-cluster-sync.rst From 2955064d7547c4310a04f4ed24fa4680473de4ed Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 19 Sep 2023 16:58:08 -0700 Subject: [PATCH 11/38] DOCSP-29504-many-to-one-clusters --- source/includes/migrationName.rst | 8 +++----- source/reference/configuration.txt | 9 +++++++++ source/reference/mongosync.txt | 7 +++++++ 3 files changed, 19 insertions(+), 5 deletions(-) diff --git a/source/includes/migrationName.rst b/source/includes/migrationName.rst index 0b0224f2a..006689f26 100644 --- a/source/includes/migrationName.rst +++ b/source/includes/migrationName.rst @@ -7,10 +7,8 @@ The ``migrationName`` string can contain a maximum of 44 alphanumeric or underscore characters. ``migrationName`` is appended to the string -``"mongosync_internal_"``. - -For example, if you set ``migrationName`` to ``"Cluster 27000 to -cluster 35000"``, the string added to the database is +``"mongosync_internal_"``. For example, if you set ``migrationName`` to +``"Cluster 27000 to cluster 35000"``, the string set in the database is ``"mongosync_internal_Cluster 27000 to cluster 35000"``. -For a full example, see :ref:`c2c-quickstart-many-with-one`. +For a complete example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/reference/configuration.txt b/source/reference/configuration.txt index d3b8dd988..a624e5b7c 100644 --- a/source/reference/configuration.txt +++ b/source/reference/configuration.txt @@ -111,6 +111,15 @@ Options To set the ``logPath`` setting from the command line, see the :option:`--logPath` option. +.. setting:: migrationName + + *Type*: string + + .. include:: /includes/opts/migrationName.rst + + To set the ``migrationName`` setting from the command line, see the + :option:`--migrationName` option. + .. setting:: port *Type*: integer diff --git a/source/reference/mongosync.txt b/source/reference/mongosync.txt index cb263e4db..0cdb35a6e 100644 --- a/source/reference/mongosync.txt +++ b/source/reference/mongosync.txt @@ -119,6 +119,13 @@ Global Options .. note:: .. include:: /includes/fact-log-rotation-usr1-signal + +.. option:: --migrationName + + .. include:: /includes/opts/migrationName.rst + + To set the ``--migrationName`` option from a configuration file, + see the :setting:`migrationName` setting. .. option:: --port From 42ca77be8eb36e074c30904f14b8665f099de6bc Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 11:22:26 -0700 Subject: [PATCH 12/38] DOCSP-29504-many-to-one-clusters --- source/quickstart.txt | 27 +++++++++++++++++++++++++-- source/reference/limitations.txt | 30 ++++++++++++++++++++++++++++++ 2 files changed, 55 insertions(+), 2 deletions(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index 7b8bb3d1f..795699254 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -306,7 +306,30 @@ Synchronization Notes - To estimate the size of ``oplog`` needed for initial synchronization, see :ref:`c2c-oplog-sizing`. -Synchronize Data from Many Clusters to One Cluster -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. _c2c-quickstart-many-with-one: + +Sync Many Source Clusters with One Destination Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/many-with-one-cluster.rst + +For limitations, see :ref:`c2c-limitations_multiple_sync`. + +The following examples connect source clusters running on port 27000 and +27001 with a destination cluster running on port 35000. The commands +also set the optional :option:`migrationName` command line option to +identify the operations. + +.. code-block:: shell + + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27000" \ + --cluster1 "mongodb://localhost:35000" \ + --migrationName "Cluster 27000 to cluster 35000" + + ./bin/mongosync \ + --cluster0 "mongodb://localhost:27001" \ + --cluster1 "mongodb://localhost:35000" \ + --migrationName "Cluster 27001 to cluster 35000" .. include:: /includes/many-to-one-cluster-sync.rst diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 4be1bc201..91f142c30 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -55,6 +55,36 @@ General Limitations - ``mongosync`` must read from the source cluster using the :readmode:`primary` read preference. +.. _c2c-limitations_multiple_sync: + +Mutiple Simultaneous Sync Limitations +------------------------------------- + +Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous +syncs into a single destination cluster. You can only sync namespaces +that don't conflict. A namespace is the +``database_name.collection_name`` combination. + +For example: + +- Two source clusters, S1 and S2, and a destination cluster D. +- Databases X and Y on both S1 and S2. +- Collections A, B, C, and D on both S1 and S2. +- You can sync: + + - ``X.A`` and ``Y.C`` on S1 with D. + - ``X.B`` and ``Y.D`` on S2 with D. + +- You cannot sync: + + - X.A and X.B on S1 with D. + - X.A and X.B on S2 with D. + + D is initially empty. You can start a non-filtered sync from S1 to + D. ``X.A`` and ``X.B`` are copied. You cannot perform another sync + from S2 to D because ``X.A`` and ``X.B`` conflict with collections + that already exist on D. + MongoDB Community Edition ------------------------- From cc3c685a87053dc902d34edc8499ceec4085953f Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 12:59:26 -0700 Subject: [PATCH 13/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 7 ++-- source/includes/migrationName-description.rst | 7 ++-- source/reference/limitations.txt | 32 +++++++++---------- 3 files changed, 24 insertions(+), 22 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index b9cb00b19..e716c80c0 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,3 +1,4 @@ -Starting in 1.7.0, ``mongosync`` can sync many source clusters with one -destination cluster. For example, you can consolidate data from many -small clusters with one centralized cluster. +Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous +syncs from different source clusters into one destination cluster. +For example, you can consolidate data from many small clusters with one +centralized cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index 6ec684ab8..5d568b508 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,3 +1,4 @@ -Starting in 1.7.0, you can set a name for a data migration. For example, -you can set a migration name to identify the sync operations from many -source clusters with one destination cluster. +Starting in ``mongosync`` 1.7.0, you can set a migration name for a data +sync operation. For example, you can set a migration name to identify +the sync operations from many source clusters into one destination +cluster. diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 91f142c30..ac72b1100 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -60,30 +60,30 @@ General Limitations Mutiple Simultaneous Sync Limitations ------------------------------------- -Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous -syncs into a single destination cluster. You can only sync namespaces -that don't conflict. A namespace is the -``database_name.collection_name`` combination. +.. include:: /includes/many-with-one-cluster.rst -For example: +A namespace is a ``database_name.collection_name`` combination. You can +only sync namespaces that don't conflict. -- Two source clusters, S1 and S2, and a destination cluster D. -- Databases X and Y on both S1 and S2. -- Collections A, B, C, and D on both S1 and S2. -- You can sync: +For example, consider this scenario: + +- Two source clusters S1 and S2. +- A destination cluster D. +- Databases ``X`` and ``Y`` on both S1 and S2. +- Collections ``A``, ``B``, ``C``, and ``D`` on both S1 and S2. +- You can sync both of these combinations: - ``X.A`` and ``Y.C`` on S1 with D. - ``X.B`` and ``Y.D`` on S2 with D. -- You cannot sync: +- You cannot sync both of these combinations: - - X.A and X.B on S1 with D. - - X.A and X.B on S2 with D. + - ``X.A`` and ``X.B`` on S1 with D. + - ``X.A`` and ``X.B`` on S2 with D. - D is initially empty. You can start a non-filtered sync from S1 to - D. ``X.A`` and ``X.B`` are copied. You cannot perform another sync - from S2 to D because ``X.A`` and ``X.B`` conflict with collections - that already exist on D. + If D is initially empty, you can sync from S1 to D. ``X.A`` and + ``X.B`` are copied from S1 to D. You cannot sync from S2 to D because + ``X.A`` and ``X.B`` conflict with the collections already on D. MongoDB Community Edition ------------------------- From 6afb4250ce1848b7b484213ee5eb44846f41fd55 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 14:05:16 -0700 Subject: [PATCH 14/38] DOCSP-29504-many-to-one-clusters --- source/includes/migrationName-description.rst | 2 +- source/includes/{ => opts}/migrationName.rst | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename source/includes/{ => opts}/migrationName.rst (100%) diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index 5d568b508..f9d98af71 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,4 @@ Starting in ``mongosync`` 1.7.0, you can set a migration name for a data sync operation. For example, you can set a migration name to identify -the sync operations from many source clusters into one destination +the sync operations from multiple source clusters into one destination cluster. diff --git a/source/includes/migrationName.rst b/source/includes/opts/migrationName.rst similarity index 100% rename from source/includes/migrationName.rst rename to source/includes/opts/migrationName.rst From 227df64c880f5998910b6f2249a63fcf5994e83b Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 14:30:56 -0700 Subject: [PATCH 15/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 2 +- source/includes/migrationName-description.rst | 6 +++--- source/includes/opts/migrationName.rst | 11 ++++++----- source/quickstart.txt | 4 ++-- source/reference/limitations.txt | 4 ++-- 5 files changed, 14 insertions(+), 13 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index e716c80c0..1d1c1e948 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,4 +1,4 @@ Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous syncs from different source clusters into one destination cluster. -For example, you can consolidate data from many small clusters with one +For example, you can consolidate data from many small clusters into one centralized cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index f9d98af71..b3fdfe835 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,4 @@ -Starting in ``mongosync`` 1.7.0, you can set a migration name for a data -sync operation. For example, you can set a migration name to identify -the sync operations from multiple source clusters into one destination +Starting in ``mongosync`` 1.7.0, you can set a migration name for a sync +operation. For example, you can set a migration name to identify the +sync operations from multiple source clusters into one destination cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 006689f26..5e3fb2be7 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -5,10 +5,11 @@ .. include:: /includes/migrationName-description.rst -The ``migrationName`` string can contain a maximum of 44 alphanumeric or -underscore characters. ``migrationName`` is appended to the string -``"mongosync_internal_"``. For example, if you set ``migrationName`` to -``"Cluster 27000 to cluster 35000"``, the string set in the database is -``"mongosync_internal_Cluster 27000 to cluster 35000"``. +The ``migrationName`` string can contain a maximum combination of 44 +alphanumeric and underscore characters. ``migrationName`` is appended to +the string ``"mongosync_internal_"``. For example, if you set +``migrationName`` to ``"Cluster 27000 to cluster 35000"``, the string +set in the database is ``"mongosync_internal_Cluster 27000 to cluster +35000"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index 795699254..f9f28b109 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -308,8 +308,8 @@ Synchronization Notes .. _c2c-quickstart-many-with-one: -Sync Many Source Clusters with One Destination Cluster -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Sync Multiple Source Clusters Simultaneously with a Destination Cluster +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. include:: /includes/many-with-one-cluster.rst diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index ac72b1100..a9239a1d2 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -57,8 +57,8 @@ General Limitations .. _c2c-limitations_multiple_sync: -Mutiple Simultaneous Sync Limitations -------------------------------------- +Multiple Source Sync Limitations +-------------------------------- .. include:: /includes/many-with-one-cluster.rst From e8bf512374737e1ceb780c030f68326a8c56b827 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 15:09:39 -0700 Subject: [PATCH 16/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 6 +++--- source/includes/opts/migrationName.rst | 11 +++++------ source/quickstart.txt | 4 ++++ source/reference/limitations.txt | 4 ++-- 4 files changed, 14 insertions(+), 11 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index 1d1c1e948..e91c74526 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,4 +1,4 @@ Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous -syncs from different source clusters into one destination cluster. -For example, you can consolidate data from many small clusters into one -centralized cluster. +sync operations from different source clusters into one destination +cluster. For example, you can consolidate data from many small clusters +into one central cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 5e3fb2be7..af29d39ab 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -5,11 +5,10 @@ .. include:: /includes/migrationName-description.rst -The ``migrationName`` string can contain a maximum combination of 44 -alphanumeric and underscore characters. ``migrationName`` is appended to -the string ``"mongosync_internal_"``. For example, if you set -``migrationName`` to ``"Cluster 27000 to cluster 35000"``, the string -set in the database is ``"mongosync_internal_Cluster 27000 to cluster -35000"``. +The ``migrationName`` string can contain up to 44 alphanumeric and +underscore characters. ``migrationName`` is appended to the string +``"mongosync_internal_"``. For example, if you set ``migrationName`` to +``"Cluster 27000 to cluster 35000"``, the final string is +``"mongosync_internal_Cluster 27000 to cluster 35000"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index f9f28b109..bc0a489d2 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -333,3 +333,7 @@ identify the operations. --migrationName "Cluster 27001 to cluster 35000" .. include:: /includes/many-to-one-cluster-sync.rst + +To start the sync operation between the source clusters and the +destination cluster, see the earlier section +:ref:`c2c-quickstart-synchronize`. diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index a9239a1d2..8d9b659b4 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -81,8 +81,8 @@ For example, consider this scenario: - ``X.A`` and ``X.B`` on S1 with D. - ``X.A`` and ``X.B`` on S2 with D. - If D is initially empty, you can sync from S1 to D. ``X.A`` and - ``X.B`` are copied from S1 to D. You cannot sync from S2 to D because + If D is initially empty, you can sync S1 with D. ``X.A`` and + ``X.B`` are copied from S1 to D. You cannot sync S2 with D because ``X.A`` and ``X.B`` conflict with the collections already on D. MongoDB Community Edition From f8d52e4fe6326eb5371826d5cdc06c71328e4d2b Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 15:51:07 -0700 Subject: [PATCH 17/38] DOCSP-29504-many-to-one-clusters --- source/includes/opts/migrationName.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index af29d39ab..3f5e69491 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -3,7 +3,9 @@ .. versionadded:: 1.7.0 -.. include:: /includes/migrationName-description.rst +Sets a migration name for a sync operation. For example, you can set a +migration name to identify the sync operations from multiple source +clusters into one destination cluster. The ``migrationName`` string can contain up to 44 alphanumeric and underscore characters. ``migrationName`` is appended to the string From 7a5f8d59893886943dc94acb2a92201be45d7435 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 16:13:58 -0700 Subject: [PATCH 18/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 2 +- source/includes/migrationName-description.rst | 5 ++--- source/quickstart.txt | 2 +- source/release-notes/1.7.txt | 2 +- 4 files changed, 5 insertions(+), 6 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index e91c74526..87affaba9 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,4 +1,4 @@ Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous sync operations from different source clusters into one destination -cluster. For example, you can consolidate data from many small clusters +cluster. For example, consolidate data from many small clusters into one central cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index b3fdfe835..e1eed1d04 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,3 @@ Starting in ``mongosync`` 1.7.0, you can set a migration name for a sync -operation. For example, you can set a migration name to identify the -sync operations from multiple source clusters into one destination -cluster. +operation. For example, set a migration name to identify the sync +operations from multiple source clusters into one destination cluster. diff --git a/source/quickstart.txt b/source/quickstart.txt index bc0a489d2..c50ebe2a8 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -317,7 +317,7 @@ For limitations, see :ref:`c2c-limitations_multiple_sync`. The following examples connect source clusters running on port 27000 and 27001 with a destination cluster running on port 35000. The commands -also set the optional :option:`migrationName` command line option to +also set the optional :option:`--migrationName` command line option to identify the operations. .. code-block:: shell diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 201e06cba..06d5d4d63 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -144,7 +144,7 @@ Set a Migration Name To set a migration name, see: - :setting:`migrationName` configuration file setting -- :option:`migrationName` command line option +- :option:`--migrationName` command line option Minimum Supported Version ------------------------- From cb10e8cb1ab1564000425299d799f2b2a95a4f41 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 16:24:40 -0700 Subject: [PATCH 19/38] DOCSP-29504-many-to-one-clusters --- source/quickstart.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index c50ebe2a8..c7f133deb 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -317,8 +317,8 @@ For limitations, see :ref:`c2c-limitations_multiple_sync`. The following examples connect source clusters running on port 27000 and 27001 with a destination cluster running on port 35000. The commands -also set the optional :option:`--migrationName` command line option to -identify the operations. +also set the optional :option:`--migrationName` string to identify the +operations for information purposes only. .. code-block:: shell From 6c36a091ecf8c4b839fcadb928f8565f5f35175f Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 16:26:32 -0700 Subject: [PATCH 20/38] DOCSP-29504-many-to-one-clusters --- source/quickstart.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index c7f133deb..871c2d864 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -317,8 +317,8 @@ For limitations, see :ref:`c2c-limitations_multiple_sync`. The following examples connect source clusters running on port 27000 and 27001 with a destination cluster running on port 35000. The commands -also set the optional :option:`--migrationName` string to identify the -operations for information purposes only. +also set the optional :option:`--migrationName` string to describe the +operations. .. code-block:: shell From 0999eb5c27ebab4f5af9ee9300e83b75906f76b6 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 16:35:05 -0700 Subject: [PATCH 21/38] DOCSP-29504-many-to-one-clusters --- source/includes/opts/migrationName.rst | 4 ++-- source/quickstart.txt | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 3f5e69491..7c253abfe 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -10,7 +10,7 @@ clusters into one destination cluster. The ``migrationName`` string can contain up to 44 alphanumeric and underscore characters. ``migrationName`` is appended to the string ``"mongosync_internal_"``. For example, if you set ``migrationName`` to -``"Cluster 27000 to cluster 35000"``, the final string is -``"mongosync_internal_Cluster 27000 to cluster 35000"``. +``"Cluster 27000 to cluster 35000 sync"``, the final string is +``"mongosync_internal_Cluster 27000 to cluster 35000 sync"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index 871c2d864..812bd3f5b 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -325,12 +325,12 @@ operations. ./bin/mongosync \ --cluster0 "mongodb://localhost:27000" \ --cluster1 "mongodb://localhost:35000" \ - --migrationName "Cluster 27000 to cluster 35000" + --migrationName "Cluster 27000 to cluster 35000 sync" ./bin/mongosync \ --cluster0 "mongodb://localhost:27001" \ --cluster1 "mongodb://localhost:35000" \ - --migrationName "Cluster 27001 to cluster 35000" + --migrationName "Cluster 27001 to cluster 35000 sync" .. include:: /includes/many-to-one-cluster-sync.rst From 1236b4008f7101b041f3966c0fc09388b7bd44e3 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 17:06:22 -0700 Subject: [PATCH 22/38] DOCSP-29504-many-to-one-clusters --- source/release-notes.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/source/release-notes.txt b/source/release-notes.txt index 9bc9d8120..dc01485fb 100644 --- a/source/release-notes.txt +++ b/source/release-notes.txt @@ -9,7 +9,6 @@ Release Notes :titlesonly: /release-notes/1.7 - /release-notes/1.6 /release-notes/1.5 /release-notes/1.4 /release-notes/1.3 From 2ee16abc55430087e5be825b66624ea91269fb54 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 17:10:01 -0700 Subject: [PATCH 23/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index 87affaba9..c4c1d4b25 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,4 +1,3 @@ -Starting in ``mongosync`` 1.7.0, you can perform multiple simultaneous -sync operations from different source clusters into one destination -cluster. For example, consolidate data from many small clusters -into one central cluster. +Starting in ``mongosync`` 1.7.0, you can sync multiple source clusters +simultaneously with a destination cluster. For example, consolidate data +from many small clusters in one central cluster. From c8d2c301f59ccbe2d989ba794b5939a2cdf1a964 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 17:12:17 -0700 Subject: [PATCH 24/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index c4c1d4b25..c95714615 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,3 +1,3 @@ Starting in ``mongosync`` 1.7.0, you can sync multiple source clusters simultaneously with a destination cluster. For example, consolidate data -from many small clusters in one central cluster. +from many small clusters into one central cluster. From ff93a48ba65d93b00c6b5d9418bdda1b5cb6bf25 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 20 Sep 2023 17:12:58 -0700 Subject: [PATCH 25/38] DOCSP-29504-many-to-one-clusters --- source/includes/opts/migrationName.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 7c253abfe..f1b9a822f 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -9,8 +9,10 @@ clusters into one destination cluster. The ``migrationName`` string can contain up to 44 alphanumeric and underscore characters. ``migrationName`` is appended to the string -``"mongosync_internal_"``. For example, if you set ``migrationName`` to -``"Cluster 27000 to cluster 35000 sync"``, the final string is -``"mongosync_internal_Cluster 27000 to cluster 35000 sync"``. +``"mongosync_internal_"``. + +For example, if you set ``migrationName`` to ``"Cluster 27000 to cluster +35000 sync"``, the final string is ``"mongosync_internal_Cluster 27000 +to cluster 35000 sync"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. From 8378d7569ca02a9d489d279042691eb538bdbf0b Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Fri, 22 Sep 2023 11:05:22 -0700 Subject: [PATCH 26/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 4 ++-- source/includes/migrationName-description.rst | 5 +++-- source/includes/opts/migrationName.rst | 10 ++++----- source/quickstart.txt | 4 ++-- source/reference/limitations.txt | 21 ++++++++++--------- 5 files changed, 23 insertions(+), 21 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index c95714615..c328a3490 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,3 +1,3 @@ Starting in ``mongosync`` 1.7.0, you can sync multiple source clusters -simultaneously with a destination cluster. For example, consolidate data -from many small clusters into one central cluster. +simultaneously with a destination cluster. For example, you can +consolidate data from many small clusters into one central cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index e1eed1d04..b3fdfe835 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,3 +1,4 @@ Starting in ``mongosync`` 1.7.0, you can set a migration name for a sync -operation. For example, set a migration name to identify the sync -operations from multiple source clusters into one destination cluster. +operation. For example, you can set a migration name to identify the +sync operations from multiple source clusters into one destination +cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index f1b9a822f..19450db0b 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -7,12 +7,12 @@ Sets a migration name for a sync operation. For example, you can set a migration name to identify the sync operations from multiple source clusters into one destination cluster. -The ``migrationName`` string can contain up to 44 alphanumeric and -underscore characters. ``migrationName`` is appended to the string +The ``migrationName`` string can contain up to 44 alphanumeric +and underscore characters. ``migrationName`` is appended to the string ``"mongosync_internal_"``. -For example, if you set ``migrationName`` to ``"Cluster 27000 to cluster -35000 sync"``, the final string is ``"mongosync_internal_Cluster 27000 -to cluster 35000 sync"``. +If you set ``migrationName`` to +``"cluster_27000_to_cluster_35000_sync"``, the final string is +``"mongosync_internal_cluster_27000_to_cluster_35000_sync"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. diff --git a/source/quickstart.txt b/source/quickstart.txt index 812bd3f5b..7600736e2 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -325,12 +325,12 @@ operations. ./bin/mongosync \ --cluster0 "mongodb://localhost:27000" \ --cluster1 "mongodb://localhost:35000" \ - --migrationName "Cluster 27000 to cluster 35000 sync" + --migrationName "cluster_27000_to_cluster_35000_sync" ./bin/mongosync \ --cluster0 "mongodb://localhost:27001" \ --cluster1 "mongodb://localhost:35000" \ - --migrationName "Cluster 27001 to cluster 35000 sync" + --migrationName "cluster_27001_to_cluster_35000_sync" .. include:: /includes/many-to-one-cluster-sync.rst diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 8d9b659b4..a11fae40a 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -69,21 +69,22 @@ For example, consider this scenario: - Two source clusters S1 and S2. - A destination cluster D. -- Databases ``X`` and ``Y`` on both S1 and S2. -- Collections ``A``, ``B``, ``C``, and ``D`` on both S1 and S2. +- Databases ``inventory`` and ``sales`` on both S1 and S2. +- Collections ``products``, ``orderLines``, ``orderStatus``, and + ``orders`` on both S1 and S2. - You can sync both of these combinations: - - ``X.A`` and ``Y.C`` on S1 with D. - - ``X.B`` and ``Y.D`` on S2 with D. + - ``inventory.products`` and ``sales.orderStatus`` on S1 with D. + - ``inventory.orderLines`` and ``sales.orders`` on S2 with D. - You cannot sync both of these combinations: - - ``X.A`` and ``X.B`` on S1 with D. - - ``X.A`` and ``X.B`` on S2 with D. - - If D is initially empty, you can sync S1 with D. ``X.A`` and - ``X.B`` are copied from S1 to D. You cannot sync S2 with D because - ``X.A`` and ``X.B`` conflict with the collections already on D. + - ``inventory.products`` and ``inventory.orderLines`` on S1 with D. If + D is initially empty, you can sync S1 with D. ``inventory.products`` + and ``inventory.orderLines`` are copied from S1 to D. + - ``inventory.products`` and ``inventory.orderLines`` on S2 with D. + You cannot sync S2 with D because ``inventory.products`` and + ``inventory.orderLines`` conflict with the namespaces already on D. MongoDB Community Edition ------------------------- From 39587bccddf30a9eff507974409642c8f0762883 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Fri, 22 Sep 2023 11:11:34 -0700 Subject: [PATCH 27/38] DOCSP-29504-many-to-one-clusters --- source/includes/opts/migrationName.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 19450db0b..2eceefe8b 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -12,7 +12,7 @@ and underscore characters. ``migrationName`` is appended to the string ``"mongosync_internal_"``. If you set ``migrationName`` to -``"cluster_27000_to_cluster_35000_sync"``, the final string is +``"cluster_27000_to_cluster_35000_sync"``, the resulting final string is ``"mongosync_internal_cluster_27000_to_cluster_35000_sync"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. From 5c619712e6d1e819c84a91b4481119e036092353 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Fri, 22 Sep 2023 11:16:52 -0700 Subject: [PATCH 28/38] DOCSP-29504-many-to-one-clusters --- source/reference/limitations.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index a11fae40a..7c698cb7b 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -69,8 +69,8 @@ For example, consider this scenario: - Two source clusters S1 and S2. - A destination cluster D. -- Databases ``inventory`` and ``sales`` on both S1 and S2. -- Collections ``products``, ``orderLines``, ``orderStatus``, and +- Databases named ``inventory`` and ``sales`` on both S1 and S2. +- Collections named ``products``, ``orderLines``, ``orderStatus``, and ``orders`` on both S1 and S2. - You can sync both of these combinations: @@ -84,7 +84,8 @@ For example, consider this scenario: and ``inventory.orderLines`` are copied from S1 to D. - ``inventory.products`` and ``inventory.orderLines`` on S2 with D. You cannot sync S2 with D because ``inventory.products`` and - ``inventory.orderLines`` conflict with the namespaces already on D. + ``inventory.orderLines`` conflict with the namespaces already on D + from the previous point. MongoDB Community Edition ------------------------- From d7cc7891a0677d13ab00ddf8795729ffaa8ec815 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Fri, 22 Sep 2023 11:34:34 -0700 Subject: [PATCH 29/38] DOCSP-29504-many-to-one-clusters --- source/reference/limitations.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 7c698cb7b..164630491 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -77,7 +77,7 @@ For example, consider this scenario: - ``inventory.products`` and ``sales.orderStatus`` on S1 with D. - ``inventory.orderLines`` and ``sales.orders`` on S2 with D. -- You cannot sync both of these combinations: +- You cannot sync both of these combinations because they conflict: - ``inventory.products`` and ``inventory.orderLines`` on S1 with D. If D is initially empty, you can sync S1 with D. ``inventory.products`` From 76f9ecd7aee352e0287ba9a1090c5ac4219ca28e Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 27 Sep 2023 14:03:14 -0700 Subject: [PATCH 30/38] DOCSP-29504-many-to-one-clusters --- source/quickstart.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index 7600736e2..47a3f7179 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -315,10 +315,10 @@ Sync Multiple Source Clusters Simultaneously with a Destination Cluster For limitations, see :ref:`c2c-limitations_multiple_sync`. -The following examples connect source clusters running on port 27000 and -27001 with a destination cluster running on port 35000. The commands -also set the optional :option:`--migrationName` string to describe the -operations. +The following examples connect source clusters running on port ``27000`` +and ``27001`` with a destination cluster running on port ``35000``. The +commands also set the optional :option:`--migrationName` string to +describe the operations. .. code-block:: shell From c3d6e423cb9c585c4a851113ac5e8526c370133a Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 8 Nov 2023 10:55:06 -0800 Subject: [PATCH 31/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 2 +- source/release-notes/1.8.txt | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index c328a3490..2825f2a95 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,3 +1,3 @@ -Starting in ``mongosync`` 1.7.0, you can sync multiple source clusters +Starting in ``mongosync`` 1.8.0, you can sync multiple source clusters simultaneously with a destination cluster. For example, you can consolidate data from many small clusters into one central cluster. diff --git a/source/release-notes/1.8.txt b/source/release-notes/1.8.txt index a5539d2f9..7ed62aec3 100644 --- a/source/release-notes/1.8.txt +++ b/source/release-notes/1.8.txt @@ -23,6 +23,10 @@ Release Notes for mongosync 1.8 New Features: +Synchronize Data Between Multiple Source Clusters Simultaneously +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/many-with-one-cluster.rst Minimum Supported Version ------------------------- From ae403c6c6221ca717e0a45052fbf5c1925f40c9e Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 8 Nov 2023 11:06:31 -0800 Subject: [PATCH 32/38] DOCSP-29504-many-to-one-clusters --- source/includes/migrationName-description.rst | 2 +- source/includes/opts/migrationName.rst | 2 +- source/release-notes.txt | 1 + 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index b3fdfe835..5d1be4826 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,4 @@ -Starting in ``mongosync`` 1.7.0, you can set a migration name for a sync +Starting in ``mongosync`` 1.8.0, you can set a migration name for a sync operation. For example, you can set a migration name to identify the sync operations from multiple source clusters into one destination cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 2eceefe8b..8602e4f0e 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -1,7 +1,7 @@ .. reference/configuration.txt .. reference/mongosync.txt -.. versionadded:: 1.7.0 +.. versionadded:: 1.8.0 Sets a migration name for a sync operation. For example, you can set a migration name to identify the sync operations from multiple source diff --git a/source/release-notes.txt b/source/release-notes.txt index dc01485fb..9bc9d8120 100644 --- a/source/release-notes.txt +++ b/source/release-notes.txt @@ -9,6 +9,7 @@ Release Notes :titlesonly: /release-notes/1.7 + /release-notes/1.6 /release-notes/1.5 /release-notes/1.4 /release-notes/1.3 From 2dcf791d8b24675805f9c442133ad82491849b71 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 8 Nov 2023 11:18:52 -0800 Subject: [PATCH 33/38] DOCSP-29504-many-to-one-clusters --- source/release-notes/1.7.txt | 10 ---------- source/release-notes/1.8.txt | 10 ++++++++++ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/source/release-notes/1.7.txt b/source/release-notes/1.7.txt index 06d5d4d63..2c61b3ca8 100644 --- a/source/release-notes/1.7.txt +++ b/source/release-notes/1.7.txt @@ -136,16 +136,6 @@ Issues Fixed: initialization if the user specified only an exclusion filter and there were no fully excluded databases. -Set a Migration Name -~~~~~~~~~~~~~~~~~~~~ - -.. include:: /includes/migrationName-description.rst - -To set a migration name, see: - -- :setting:`migrationName` configuration file setting -- :option:`--migrationName` command line option - Minimum Supported Version ------------------------- diff --git a/source/release-notes/1.8.txt b/source/release-notes/1.8.txt index 7ed62aec3..8e257a065 100644 --- a/source/release-notes/1.8.txt +++ b/source/release-notes/1.8.txt @@ -28,6 +28,16 @@ Synchronize Data Between Multiple Source Clusters Simultaneously .. include:: /includes/many-with-one-cluster.rst +Set a Migration Name +~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/migrationName-description.rst + +To set a migration name, see: + +- :setting:`migrationName` configuration file setting +- :option:`--migrationName` command line option + Minimum Supported Version ------------------------- From 6ab48fec3eb58fbb61ca7d7c4a332496530b3e76 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 29 Nov 2023 11:44:29 -0800 Subject: [PATCH 34/38] DOCSP-29504-many-to-one-clusters --- source/includes/migrationName-description.rst | 4 ++-- source/includes/opts/migrationName.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index 5d1be4826..a5c9d1964 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,4 @@ Starting in ``mongosync`` 1.8.0, you can set a migration name for a sync -operation. For example, you can set a migration name to identify the -sync operations from multiple source clusters into one destination +operation. For example, you can set a migration name to identify each +sync operation from multiple source clusters into one destination cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 8602e4f0e..8d31bda9d 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -4,7 +4,7 @@ .. versionadded:: 1.8.0 Sets a migration name for a sync operation. For example, you can set a -migration name to identify the sync operations from multiple source +migration name to identify each sync operation from multiple source clusters into one destination cluster. The ``migrationName`` string can contain up to 44 alphanumeric From 883c02b3a6eb1c285378be3e69041183a3e938d4 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Wed, 6 Dec 2023 11:51:33 -0800 Subject: [PATCH 35/38] DOCSP-29504-many-to-one-clusters --- source/includes/opts/migrationName.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index 8d31bda9d..b9b98991b 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -9,10 +9,11 @@ clusters into one destination cluster. The ``migrationName`` string can contain up to 44 alphanumeric and underscore characters. ``migrationName`` is appended to the string -``"mongosync_internal_"``. +``"mongosync_internal_"`` to set the migration metadata database name. If you set ``migrationName`` to -``"cluster_27000_to_cluster_35000_sync"``, the resulting final string is +``"cluster_27000_to_cluster_35000_sync"``, the resulting ``mongosync`` +metadata database name is ``"mongosync_internal_cluster_27000_to_cluster_35000_sync"``. For a complete example, see :ref:`c2c-quickstart-many-with-one`. From 5df8b18ddac20edefc4246ca455f3b02feb3ea21 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 7 May 2024 10:19:43 -0700 Subject: [PATCH 36/38] DOCSP-29504-many-to-one-clusters --- source/quickstart.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/quickstart.txt b/source/quickstart.txt index 47a3f7179..af6a40336 100644 --- a/source/quickstart.txt +++ b/source/quickstart.txt @@ -195,6 +195,8 @@ Initialization Notes ` command. "cluster0" and "cluster1" are just labels, either cluster can be ``cluster0`` or ``cluster1``. +.. _c2c-quickstart-synchronize: + Synchronize Data Between Clusters --------------------------------- @@ -332,7 +334,7 @@ describe the operations. --cluster1 "mongodb://localhost:35000" \ --migrationName "cluster_27001_to_cluster_35000_sync" -.. include:: /includes/many-to-one-cluster-sync.rst +.. include:: /includes/many-with-one-cluster.rst To start the sync operation between the source clusters and the destination cluster, see the earlier section From f5c583af114e0b8fe1ea173f78deebe8b1b94fa1 Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Tue, 7 May 2024 11:49:59 -0700 Subject: [PATCH 37/38] DOCSP-29504-many-to-one-clusters --- source/includes/many-with-one-cluster.rst | 4 ++-- source/includes/migrationName-description.rst | 6 +++--- source/includes/opts/migrationName.rst | 9 ++++----- source/reference/limitations.txt | 2 +- 4 files changed, 10 insertions(+), 11 deletions(-) diff --git a/source/includes/many-with-one-cluster.rst b/source/includes/many-with-one-cluster.rst index 2825f2a95..a3bec7f4d 100644 --- a/source/includes/many-with-one-cluster.rst +++ b/source/includes/many-with-one-cluster.rst @@ -1,3 +1,3 @@ -Starting in ``mongosync`` 1.8.0, you can sync multiple source clusters +Starting in ``mongosync-beta`` 1.8, you can sync multiple source clusters simultaneously with a destination cluster. For example, you can -consolidate data from many small clusters into one central cluster. +consolidate data from many small clusters into a central cluster. diff --git a/source/includes/migrationName-description.rst b/source/includes/migrationName-description.rst index a5c9d1964..5ab82d6e0 100644 --- a/source/includes/migrationName-description.rst +++ b/source/includes/migrationName-description.rst @@ -1,4 +1,4 @@ -Starting in ``mongosync`` 1.8.0, you can set a migration name for a sync -operation. For example, you can set a migration name to identify each -sync operation from multiple source clusters into one destination +Starting in ``mongosync-beta`` 1.8, you can set a migration name for a +sync operation. For example, you can set a migration name to identify +each sync operation from multiple source clusters into a destination cluster. diff --git a/source/includes/opts/migrationName.rst b/source/includes/opts/migrationName.rst index b9b98991b..f9c914d58 100644 --- a/source/includes/opts/migrationName.rst +++ b/source/includes/opts/migrationName.rst @@ -1,11 +1,10 @@ .. reference/configuration.txt .. reference/mongosync.txt -.. versionadded:: 1.8.0 - -Sets a migration name for a sync operation. For example, you can set a -migration name to identify each sync operation from multiple source -clusters into one destination cluster. +Starting in ``mongosync-beta`` 1.8, sets a migration name for a sync +operation. For example, you can set a migration name to identify each +sync operation from multiple source clusters into one destination +cluster. The ``migrationName`` string can contain up to 44 alphanumeric and underscore characters. ``migrationName`` is appended to the string diff --git a/source/reference/limitations.txt b/source/reference/limitations.txt index 164630491..c91f681e3 100644 --- a/source/reference/limitations.txt +++ b/source/reference/limitations.txt @@ -85,7 +85,7 @@ For example, consider this scenario: - ``inventory.products`` and ``inventory.orderLines`` on S2 with D. You cannot sync S2 with D because ``inventory.products`` and ``inventory.orderLines`` conflict with the namespaces already on D - from the previous point. + from the scenario in the previous point. MongoDB Community Edition ------------------------- From 34cd153b1ea73b51127700d9837a43d1cdbd481b Mon Sep 17 00:00:00 2001 From: jason-price-mongodb Date: Thu, 9 May 2024 12:01:54 -0700 Subject: [PATCH 38/38] DOCSP-29504-many-to-one-clusters --- source/release-notes/1.8.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/release-notes/1.8.txt b/source/release-notes/1.8.txt index 8e257a065..0f141a68a 100644 --- a/source/release-notes/1.8.txt +++ b/source/release-notes/1.8.txt @@ -21,7 +21,7 @@ Release Notes for mongosync 1.8 **Upcoming** -New Features: +Beta Features: Synchronize Data Between Multiple Source Clusters Simultaneously ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~