lboka/document-database-service
1
0
Fork 0
forked from docs/document-database-service
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-09-08 06:45:57 +00:00
parent 2aaa6b3716
commit 4de5ce0fb1
7 changed files with 237 additions and 175 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

92
umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_private_networks/creating_a_cluster_instance.rst
View File

@ -21,49 +21,55 @@ Procedure
.. table:: **Table 1** Basic information .. table:: **Table 1** Basic information
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+=============================================================================================================================================================================================================================+ +===================================+=====================================================================================================================================================================================================================================================================================+
| Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Exercise caution when selecting a region. | | | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Exercise caution when selecting a region. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). | | DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). |
| | | | | |
| | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. | | | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Database Type | Community Edition | | Database Type | Community Edition |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Type | Select **Cluster**. | | DB Instance Type | Select **Cluster**. |
| | | | | |
| | 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. | | | 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.4 | | Compatible MongoDB Version | - 4.4 |
| | - 4.2 | | | - 4.2 |
| | - 4.0 | | | - 4.0 |
| | - 3.4 | | | - 3.4 |
| | - 3.2 | | | - 3.2 |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| AZ | An AZ is a part of a region with its own independent power supply and network. AZs are physically isolated but can communicate through an internal network. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| Disk Encryption | - **Disabled**: Disable the encryption function. | | | - RocksDB |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | **Key Name**: Select or create a private key, which is the tenant key. | | AZ | An AZ is a part of a region with its own independent power supply and network. AZs are physically isolated but can communicate through an internal network. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | .. note:: | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | **Key Name**: Select or create a private key, which is the tenant key. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| | .. note:: |
| | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications .. table:: **Table 2** Specifications

92
umn/source/getting_started_with_clusters/connecting_to_a_cluster_instance_over_public_networks/creating_a_cluster_instance.rst
View File

@ -21,49 +21,55 @@ Procedure
.. table:: **Table 1** Basic information .. table:: **Table 1** Basic information
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+=============================================================================================================================================================================================================================+ +===================================+=====================================================================================================================================================================================================================================================================================+
| Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Exercise caution when selecting a region. | | | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Exercise caution when selecting a region. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). | | DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). |
| | | | | |
| | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. | | | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Database Type | Community Edition | | Database Type | Community Edition |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Type | Select **Cluster**. | | DB Instance Type | Select **Cluster**. |
| | | | | |
| | 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. | | | 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.4 | | Compatible MongoDB Version | - 4.4 |
| | - 4.2 | | | - 4.2 |
| | - 4.0 | | | - 4.0 |
| | - 3.4 | | | - 3.4 |
| | - 3.2 | | | - 3.2 |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| AZ | An AZ is a part of a region with its own independent power supply and network. AZs are physically isolated but can communicate through an internal network. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| Disk Encryption | - **Disabled**: Disable the encryption function. | | | - RocksDB |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | **Key Name**: Select or create a private key, which is the tenant key. | | AZ | An AZ is a part of a region with its own independent power supply and network. AZs are physically isolated but can communicate through an internal network. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | .. note:: | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | **Key Name**: Select or create a private key, which is the tenant key. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| | .. note:: |
| | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications .. table:: **Table 2** Specifications

8
umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_private_networks/creating_a_replica_set_instance.rst
View File

@ -48,7 +48,13 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
| | |
| | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
| | |
| | - RocksDB |
| | |
| | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |

8
umn/source/getting_started_with_replica_sets/connecting_to_a_replica_set_instance_over_public_networks/creating_a_replica_set_instance.rst
View File

@ -48,7 +48,13 @@ You can use your account to create up to 50 replica set instances. To create mor
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
| | |
| | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
| | |
| | - RocksDB |
| | |
| | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
+-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |

92
umn/source/getting_started_with_single_nodes/connecting_to_a_single-node_instance_over_private_networks/creating_a_single_node_instance.rst
View File

@ -21,49 +21,55 @@ Procedure
.. table:: **Table 1** Basic information .. table:: **Table 1** Basic information
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+===================================================================================================================================================================================================================================================+ +===================================+=====================================================================================================================================================================================================================================================================================+
| Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Therefore, you should exercise caution when selecting a region. | | | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Therefore, you should exercise caution when selecting a region. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). | | DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). |
| | | | | |
| | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. | | | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Database Type | Community Edition | | Database Type | Community Edition |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Type | Select **Single Node**. | | DB Instance Type | Select **Single Node**. |
| | | | | |
| | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. | | | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Compatible MongoDB Version | - 4.4 | | Compatible MongoDB Version | - 4.4 |
| | - 4.2 | | | - 4.2 |
| | - 4.0 | | | - 4.0 |
| | - 3.4 | | | - 3.4 |
| | - 3.2 | | | - 3.2 |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| Disk Encryption | - **Disabled**: Disable the encryption function. | | | - RocksDB |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | **Key Name**: Select or create a private key, which is the tenant key. | | AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | .. note:: | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | **Key Name**: Select or create a private key, which is the tenant key. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| | .. note:: |
| | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications .. table:: **Table 2** Specifications

92
umn/source/getting_started_with_single_nodes/connecting_to_a_single_node_instance_over_public_networks/creating_a_single_node_instance.rst
View File

@ -21,49 +21,55 @@ Procedure
.. table:: **Table 1** Basic information .. table:: **Table 1** Basic information
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Parameter | Description | | Parameter | Description |
+===================================+===================================================================================================================================================================================================================================================+ +===================================+=====================================================================================================================================================================================================================================================================================+
| Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | Region | A region where the tenant is located. It can be changed in the upper left corner. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | | | |
| | .. note:: | | | .. note:: |
| | | | | |
| | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Therefore, you should exercise caution when selecting a region. | | | DB instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of a DB instance once it is created. Therefore, you should exercise caution when selecting a region. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). | | DB Instance Name | The DB instance name can be 4 to 64 characters long. It must start with a letter and can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_). |
| | | | | |
| | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. | | | After the DB instance is created, you can change the DB instance name. For details, see section :ref:`Changing a DB Instance Name <dds_03_0075>`. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Database Type | Community Edition | | Database Type | Community Edition |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| DB Instance Type | Select **Single Node**. | | DB Instance Type | Select **Single Node**. |
| | | | | |
| | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. | | | The single node architecture is another option for you, helping you reduce costs while ensuring data reliability. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Compatible MongoDB Version | - 4.4 | | Compatible MongoDB Version | - 4.4 |
| | - 4.2 | | | - 4.2 |
| | - 4.0 | | | - 4.0 |
| | - 3.4 | | | - 3.4 |
| | - 3.2 | | | - 3.2 |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Type | Ultra-high I/O | | Storage Type | Ultra-high I/O |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Storage Engine | WiredTiger | | Storage Engine | - WiredTiger |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. | | | WiredTiger is the default storage engine of DDS 3.2, 3.4 and 4.0. WiredTiger provides different granularity concurrency control and compression mechanism for data management. It can provide the best performance and storage efficiency for different kinds of applications. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| Disk Encryption | - **Disabled**: Disable the encryption function. | | | - RocksDB |
| | | | | |
| | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. | | | RocksDB is the default storage engine of DDS 4.2 and 4.4. RocksDB supports efficient point lookup, range scan, and high-speed write. RocksDB can be used as the underlying data storage engine of MongoDB and is suitable for scenarios with a large number of write operations. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | **Key Name**: Select or create a private key, which is the tenant key. | | AZ | An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. For details, see section :ref:`Regions and AZs <dds_01_0027>`. |
| | | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | .. note:: | | Disk Encryption | - **Disabled**: Disable the encryption function. |
| | | | | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. | | | - **Enabled**: Enable the encryption function. This feature improves data security but slightly affects read/write performance. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. | | | |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. | | | **Key Name**: Select or create a private key, which is the tenant key. |
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | |
| | .. note:: |
| | |
| | - After a DB instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. |
| | - The key cannot be disabled or deleted when being used. Otherwise, the database becomes unavailable. |
| | - For details about how to create a key, see the "Creating a CMK" section in the *Key Management Service User Guide*. |
+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
.. table:: **Table 2** Specifications .. table:: **Table 2** Specifications

28
umn/source/introduction/dds_db_instance/database_engine_and_version.rst
View File

@ -5,4 +5,30 @@
Database Engine and Version Database Engine and Version
=========================== ===========================
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. DDS supports versions 3.2, 3.4, 4.0, 4.2, and 4.4, and you need to use a driver compatible with MongoDB 3.0 or later to access DDS. You can select the DB engine and version you need based on your service requirements.
.. table:: **Table 1** Supported DB engines and versions
+-----------------------+-----------------------+-----------------------+
| Compatibility | DB Instance Type | Storage Engine |
+=======================+=======================+=======================+
| 4.4 | - Cluster | RocksDB |
| | - Replica set | |
| | - Single | |
+-----------------------+-----------------------+-----------------------+
| 4.2 | - Cluster | RocksDB |
| | - Replica set | |
| | - Single | |
+-----------------------+-----------------------+-----------------------+
| 4.0 | - Cluster | WiredTiger |
| | - Replica set | |
| | - Single | |
+-----------------------+-----------------------+-----------------------+
| 3.4 | - Cluster | WiredTiger |
| | - Replica set | |
| | - Single | |
+-----------------------+-----------------------+-----------------------+
| 3.2 | - Cluster | WiredTiger |
| | - Replica set | |
| | - Single | |
+-----------------------+-----------------------+-----------------------+