From 2aaa6b371618287d29bc7fcb216c314a850cb55e Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Tue, 5 Sep 2023 07:49:28 +0000 Subject: [PATCH] Update content --- .../enabling_ip_addresses_of_shard_and_config_nodes.rst | 2 +- .../creating_a_cluster_instance.rst | 3 ++- .../creating_a_cluster_instance.rst | 3 ++- .../creating_a_replica_set_instance.rst | 3 ++- .../creating_a_replica_set_instance.rst | 3 ++- .../creating_a_single_node_instance.rst | 3 ++- .../creating_a_single_node_instance.rst | 3 ++- .../dds_db_instance/database_engine_and_version.rst | 2 +- 8 files changed, 14 insertions(+), 8 deletions(-) diff --git a/umn/source/connection_management/enabling_ip_addresses_of_shard_and_config_nodes.rst b/umn/source/connection_management/enabling_ip_addresses_of_shard_and_config_nodes.rst index d0856b4..1fc9ae4 100644 --- a/umn/source/connection_management/enabling_ip_addresses_of_shard_and_config_nodes.rst +++ b/umn/source/connection_management/enabling_ip_addresses_of_shard_and_config_nodes.rst @@ -15,7 +15,7 @@ This section describes how to obtain the IP addresses of the shard and config no Before You Start ---------------- -- DDS supports cluster instances of Community Edition 3.2, 3.4, 4.0, and 4.2. +- DDS supports cluster instances of Community Edition 3.2, 3.4, 4.0, 4.2, and 4.4. - DDS creates two connection addresses for the primary node and secondary node in a shard respectively. - Once the connection addresses are assigned to your nodes, they cannot be modified or deleted. - The connection address is accessible from private networks only. diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst index 4e6e63e..483411b 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst @@ -40,7 +40,8 @@ Procedure | | | | | A cluster instance includes three types of nodes: mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst index 6dbeb69..89c712b 100644 --- a/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst +++ b/umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst @@ -40,7 +40,8 @@ Procedure | | | | | A cluster instance includes three types of nodes: mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst index 889af38..302445e 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst @@ -40,7 +40,8 @@ You can use your account to create up to 50 replica set instances. To create mor | | | | | A replica set consists of the primary node, secondary node, and hidden node. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst index 04b51cc..79f5fe0 100644 --- a/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst +++ b/umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst @@ -40,7 +40,8 @@ You can use your account to create up to 50 replica set instances. To create mor | | | | | A replica set consists of the primary node, secondary node, and hidden node. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability. | +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst index 3249cbd..d7aeff2 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst @@ -40,7 +40,8 @@ Procedure | | | | | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst index 20bde1f..1d1c87a 100644 --- a/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst +++ b/umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst @@ -40,7 +40,8 @@ Procedure | | | | | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Compatible MongoDB Version | - 4.2 | + | Compatible MongoDB Version | - 4.4 | + | | - 4.2 | | | - 4.0 | | | - 3.4 | | | - 3.2 | diff --git a/umn/source/introduction/dds_db_instance/database_engine_and_version.rst b/umn/source/introduction/dds_db_instance/database_engine_and_version.rst index 9836bf0..8ecb837 100644 --- a/umn/source/introduction/dds_db_instance/database_engine_and_version.rst +++ b/umn/source/introduction/dds_db_instance/database_engine_and_version.rst @@ -5,4 +5,4 @@ Database Engine and Version =========================== -DDS is compatible with MongoDB 3.2, 3.4, 4.0, and 4.2 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.0 or later to access DDS. +DDS is compatible with MongoDB 3.2, 3.4, 4.0, 4.2, and 4.4 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.0 or later to access DDS.