diff --git a/docs/dds/umn/ALL_META.TXT.json b/docs/dds/umn/ALL_META.TXT.json index 9c8d1eb59..e96d46f0d 100644 --- a/docs/dds/umn/ALL_META.TXT.json +++ b/docs/dds/umn/ALL_META.TXT.json @@ -61,7 +61,7 @@ "node_id":"dds_01_0011.xml", "product_code":"dds", "code":"4", - "des":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.Data read and write requests are fo", + "des":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.Data read and write requests ar", "doc_type":"usermanual", "kw":"Cluster,System Architecture,User Guide", "search_title":"", @@ -133,7 +133,7 @@ "node_id":"dds_01_0002.xml", "product_code":"dds", "code":"8", - "des":"Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and w", + "des":"Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.A dds mongos is a router for readi", "doc_type":"usermanual", "kw":"Cluster,Basic Concepts,User Guide", "search_title":"", @@ -493,7 +493,7 @@ "node_id":"dds_02_0022.xml", "product_code":"dds", "code":"28", - "des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule", + "des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.", "doc_type":"usermanual", "kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Private Networks,Use", "search_title":"", @@ -601,7 +601,7 @@ "node_id":"dds_02_0019.xml", "product_code":"dds", "code":"34", - "des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule", + "des":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.", "doc_type":"usermanual", "kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Public Networks,User", "search_title":"", @@ -619,7 +619,7 @@ "node_id":"dds_02_0006.xml", "product_code":"dds", "code":"35", - "des":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a DB i", + "des":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB client an", "doc_type":"usermanual", "kw":"DB instance,Connecting to a Cluster Instance Over Public Networks,Connecting to a Cluster Instance O", "search_title":"", @@ -745,7 +745,7 @@ "node_id":"en-us_topic_0105284966.xml", "product_code":"dds", "code":"42", - "des":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.You can directly perform operations on the primary and seco", + "des":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.You can directly perform ope", "doc_type":"usermanual", "kw":"DDS DB instance,DDS DB instance,Connecting to a Replica Set Instance Over Private Networks,Connectin", "search_title":"", @@ -853,7 +853,7 @@ "node_id":"dds_02_0047.xml", "product_code":"dds", "code":"48", - "des":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.You can directly perform operations on the prima", + "des":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.You can directly ", "doc_type":"usermanual", "kw":"DDS DB instance,Connecting to a Replica Set Instance Over Public Networks,Connecting to a Replica Se", "search_title":"", @@ -979,7 +979,7 @@ "node_id":"dds_02_0028.xml", "product_code":"dds", "code":"55", - "des":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an une", + "des":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.The MongoDB client can conne", "doc_type":"usermanual", "kw":"DDS DB instance,DDS DB instance,Connecting to a Single Node Instance Over Private Networks,Connectin", "search_title":"", @@ -1087,7 +1087,7 @@ "node_id":"dds_02_0048.xml", "product_code":"dds", "code":"61", - "des":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a ", + "des":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB clien", "doc_type":"usermanual", "kw":"DDS DB instance,Connecting to a Single Node Instance Over Public Networks,Connecting to a Single Nod", "search_title":"", @@ -1219,7 +1219,7 @@ "node_id":"dds_02_0100.xml", "product_code":"dds", "code":"68", - "des":"A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to th", + "des":"A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect t", "doc_type":"usermanual", "kw":"Enabling IP Addresses of shard and config Nodes,Connection Management,User Guide", "search_title":"", @@ -1327,7 +1327,7 @@ "node_id":"dds_03_0052.xml", "product_code":"dds", "code":"74", - "des":"DDS is accessible through an EIP in a public network or an ECS in a private network.MongoDB can export data from a database into a JSON file. Such a JSON file can then be", + "des":"DDS is accessible through an EIP in a public network or an ECS in a private network.DDS is compatible with MongoDB.MongoDB can export data from a database into a JSON fil", "doc_type":"usermanual", "kw":"Migrating Data,User Guide", "search_title":"", @@ -2047,7 +2047,7 @@ "node_id":"dds_03_0040.xml", "product_code":"dds", "code":"114", - "des":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a snapshot backupCreating a cluster InstanceCreating a r", + "des":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a cluster InstanceCreating a replica set instanceCreatin", "doc_type":"usermanual", "kw":"Task Center,User Guide", "search_title":"", diff --git a/docs/dds/umn/CLASS.TXT.json b/docs/dds/umn/CLASS.TXT.json index c5e13bb01..1b48724cf 100644 --- a/docs/dds/umn/CLASS.TXT.json +++ b/docs/dds/umn/CLASS.TXT.json @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.Data read and write requests are fo", + "desc":"Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.Data read and write requests ar", "product_code":"dds", "title":"Cluster", "uri":"dds_01_0011.html", @@ -63,7 +63,7 @@ "code":"7" }, { - "desc":"Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and w", + "desc":"Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.A dds mongos is a router for readi", "product_code":"dds", "title":"Cluster", "uri":"dds_01_0002.html", @@ -243,7 +243,7 @@ "code":"27" }, { - "desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule", + "desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.", "product_code":"dds", "title":"Setting a Security Group", "uri":"dds_02_0022.html", @@ -297,7 +297,7 @@ "code":"33" }, { - "desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.The default security group rule", + "desc":"This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.", "product_code":"dds", "title":"Setting a Security Group", "uri":"dds_02_0019.html", @@ -306,7 +306,7 @@ "code":"34" }, { - "desc":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a DB i", + "desc":"This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB client an", "product_code":"dds", "title":"Connecting to a Cluster Instance Over Public Networks", "uri":"dds_02_0006.html", @@ -369,7 +369,7 @@ "code":"41" }, { - "desc":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.You can directly perform operations on the primary and seco", + "desc":"This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.You can directly perform ope", "product_code":"dds", "title":"Connecting to a Replica Set Instance Over Private Networks", "uri":"en-us_topic_0105284966.html", @@ -423,7 +423,7 @@ "code":"47" }, { - "desc":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.You can directly perform operations on the prima", + "desc":"This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.You can directly ", "product_code":"dds", "title":"Connecting to a Replica Set Instance Over Public Networks", "uri":"dds_02_0047.html", @@ -486,7 +486,7 @@ "code":"54" }, { - "desc":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an une", + "desc":"This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.The MongoDB client can conne", "product_code":"dds", "title":"Connecting to a Single Node Instance Over Private Networks", "uri":"dds_02_0028.html", @@ -540,7 +540,7 @@ "code":"60" }, { - "desc":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.The MongoDB client and Robo 3T can connect to a ", + "desc":"This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.The MongoDB clien", "product_code":"dds", "title":"Connecting to a Single Node Instance Over Public Networks", "uri":"dds_02_0048.html", @@ -603,7 +603,7 @@ "code":"67" }, { - "desc":"A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to th", + "desc":"A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect t", "product_code":"dds", "title":"Enabling IP Addresses of shard and config Nodes", "uri":"dds_02_0100.html", @@ -657,7 +657,7 @@ "code":"73" }, { - "desc":"DDS is accessible through an EIP in a public network or an ECS in a private network.MongoDB can export data from a database into a JSON file. Such a JSON file can then be", + "desc":"DDS is accessible through an EIP in a public network or an ECS in a private network.DDS is compatible with MongoDB.MongoDB can export data from a database into a JSON fil", "product_code":"dds", "title":"Migrating Data", "uri":"dds_03_0052.html", @@ -1017,7 +1017,7 @@ "code":"113" }, { - "desc":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a snapshot backupCreating a cluster InstanceCreating a r", + "desc":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Creating a cluster InstanceCreating a replica set instanceCreatin", "product_code":"dds", "title":"Task Center", "uri":"dds_03_0040.html", diff --git a/docs/dds/umn/dds_01_0002.html b/docs/dds/umn/dds_01_0002.html index 34d29d27d..e69d67999 100644 --- a/docs/dds/umn/dds_01_0002.html +++ b/docs/dds/umn/dds_01_0002.html @@ -1,10 +1,10 @@

Cluster

-

Each DDS cluster consists of a config node, and multiple mongos and shard nodes. The following diagram shows the node relationships.

-
Figure 1 Diagram of node relationships
-

mongos

A mongos is a router for reading and writing data, providing a unified interface for accessing DB instances.

- +

Each DDS cluster consists of a config node, and multiple dds mongos and shard nodes. The following diagram shows the node relationships.

+
Figure 1 Diagram of node relationships
+

dds mongos

A dds mongos is a router for reading and writing data, providing a unified interface for accessing DB instances.

+
  • Each DB instance has 2 to 32 dds mongos. You can specify the quantity.
  • A dds mongos reads configuration settings from configs and allocates read and write requests to shards. You can connect to a dds mongos directly.

config

A config stores configuration settings for DB instances and consists of one replica set.

  • The availability of a config is the prerequisite to deploying a DB instance or modifying the instance information.
  • You cannot connect to a config directly.
diff --git a/docs/dds/umn/dds_01_0006.html b/docs/dds/umn/dds_01_0006.html index 395447b3b..1307f4ce3 100644 --- a/docs/dds/umn/dds_01_0006.html +++ b/docs/dds/umn/dds_01_0006.html @@ -2,14 +2,14 @@

Functions and Features

Three Architectures

DDS supports three deployment architectures: cluster, replica set, and single node. They meet requirements of different service scenarios.

-
  • Cluster

    A cluster consists of three types of nodes: mongos, shard, and config. You can select the number and configuration of mongos and shard nodes to create cluster instances with different levels of service performance.

    +
    • Cluster

      A cluster consists of three types of nodes: dds mongos, shard, and config. You can select the number and configuration of dds mongos and shard nodes to create cluster instances with different levels of service performance.

    • Replica set

      DDS automatically builds the replica set architecture, and you can directly operate the primary and secondary nodes. DDS provides you with advanced functions such as high availability (HA) and disaster recovery (DR) switchover, and is invisible to applications.

    • Single node

      A database that is deployed on a single VM does not have the HA feature. To ensure data consistency during full backup, tables are locked to prevent data from being changed. The single-node architecture features low costs and is a preferred option for R&D and testing environment, learning and training environment, and internal systems of small-sized enterprises.

-

Elastic Scaling

With the development of your services, you can change CPU and memory specifications of instances, expand storage space, and add mongos and shard nodes of cluster DB instances in real time. You are advised to perform the change during off-peak hours to avoid the impact of changes on your services.

+

Elastic Scaling

With the development of your services, you can change CPU and memory specifications of instances, expand storage space, and add dds mongos and shard nodes of cluster DB instances in real time. You are advised to perform the change during off-peak hours to avoid the impact of changes on your services.

Key Features

-
Table 1 Key feature description

Features

diff --git a/docs/dds/umn/dds_01_0011.html b/docs/dds/umn/dds_01_0011.html index 11da3af67..00eea4ad0 100644 --- a/docs/dds/umn/dds_01_0011.html +++ b/docs/dds/umn/dds_01_0011.html @@ -1,10 +1,10 @@

Cluster

-

Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.

-

Data read and write requests are forwarded by the mongos nodes, which read configuration settings from config, and then allocate the read and write requests to the shards, making it easy to cope with high concurrency scenarios. In addition, each config node, along with the shards in its cluster, is replicated in triplicate to ensure high availability. The following figure shows the DDS cluster architecture.

-
Figure 1 Cluster architecture
-
  • A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see official documents.
  • Each mongos is a single node, but you can provision multiple mongos nodes for load balancing and failovers. A single cluster can contain 2 to 32 mongos nodes.
  • Each shard is a three-node replica set, and each cluster can contain 2 to 32 shards.
  • A config node is a necessary part of a cluster instance, and is also deployed as a replica set. The config node stores instance configuration data.
  • The number of mongos and shard nodes can be increased from the management console. You do not need to use native commands.
  • You can enable IP addresses of shards and the config node to directly access the shards and the config node.
  • A three-node replica set cannot be directly upgraded to a cluster.
+

Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple dds mongos and shard nodes.

+

Data read and write requests are forwarded by the dds mongos nodes, which read configuration settings from config, and then allocate the read and write requests to the shards, making it easy to cope with high concurrency scenarios. In addition, each config node, along with the shards in its cluster, is replicated in triplicate to ensure high availability. The following figure shows the DDS cluster architecture.

+
Figure 1 Cluster architecture
+
  • A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see official documents.
  • Each dds mongos is a single node, but you can provision multiple dds mongos nodes for load balancing and failovers. A single cluster can contain 2 to 32 dds mongos nodes.
  • Each shard is a three-node replica set, and each cluster can contain 2 to 32 shards.
  • A config node is a necessary part of a cluster instance, and is also deployed as a replica set. The config node stores instance configuration data.
  • The number of dds mongos and shard nodes can be increased from the management console. You do not need to use native commands.
  • You can enable IP addresses of shards and the config node to directly access the shards and the config node.
  • A three-node replica set cannot be directly upgraded to a cluster.
diff --git a/docs/dds/umn/dds_01_0015.html b/docs/dds/umn/dds_01_0015.html index 3eea00821..17a0b5c29 100644 --- a/docs/dds/umn/dds_01_0015.html +++ b/docs/dds/umn/dds_01_0015.html @@ -6,7 +6,7 @@

Advantages:

  • Supports embedded documents that eliminate the need to use joins to reduce application development complexity. Flexible schemas also facilitate rapid development and iteration.
  • Sharded clusters provide enough capacity to store data into the TB range.
-

IoT

DDS is compatible with MongoDB and provides the high-performance and asynchronous data write function. In certain scenarios, DDS can process data in the memory database. In addition, cluster instances can dynamically add the number of mongos and shard nodes or upgrade specifications. The performance and storage space can be quickly expanded, making cluster instances suitable for IoT scenarios with high concurrent writes.

+

IoT

DDS is compatible with MongoDB and provides the high-performance and asynchronous data write function. In certain scenarios, DDS can process data in the memory database. In addition, cluster instances can dynamically add the number of dds mongos and shard nodes or upgrade specifications. The performance and storage space can be quickly expanded, making cluster instances suitable for IoT scenarios with high concurrent writes.

Intelligent IoT terminals need to collect various types of data, store device logs, and analyze information in multiple dimensions. In recent years, IoT services have grown rapidly, with huge volumes of data and increasing access traffic that require horizontal expansion capabilities for data storage.

DDS provides the secondary index to meet dynamic query requirements and uses the MapReduce aggregation framework that is compatible with MongoDB to analyze data from multiple dimensions.

Advantages:

diff --git a/docs/dds/umn/dds_01_0022.html b/docs/dds/umn/dds_01_0022.html index d0c0364c1..e1b95cda1 100644 --- a/docs/dds/umn/dds_01_0022.html +++ b/docs/dds/umn/dds_01_0022.html @@ -44,7 +44,7 @@

Nodes

Mongos and shard nodes that are successfully added cannot be deleted.

+

dds mongos and shard nodes that are successfully added cannot be deleted.

Restarting a DB instance or a node

diff --git a/docs/dds/umn/dds_01_0024.html b/docs/dds/umn/dds_01_0024.html index cffc4d246..b0a1a4a17 100644 --- a/docs/dds/umn/dds_01_0024.html +++ b/docs/dds/umn/dds_01_0024.html @@ -34,7 +34,7 @@ -
- @@ -64,7 +64,7 @@ diff --git a/docs/dds/umn/dds_02_0016.html b/docs/dds/umn/dds_02_0016.html index 09b3cd88f..9a22251fd 100644 --- a/docs/dds/umn/dds_02_0016.html +++ b/docs/dds/umn/dds_02_0016.html @@ -34,7 +34,7 @@ @@ -63,7 +63,7 @@ @@ -77,19 +77,19 @@ - - - - - - diff --git a/docs/dds/umn/dds_02_0019.html b/docs/dds/umn/dds_02_0019.html index 072c50467..87e13dc33 100644 --- a/docs/dds/umn/dds_02_0019.html +++ b/docs/dds/umn/dds_02_0019.html @@ -1,7 +1,7 @@

Setting a Security Group

-

Scenarios

This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.

+

Scenarios

This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.

Precautions

The default security group rule allows all outgoing data packets. ECSs and DDS DB instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the DB instances that are in it.

To access a DB instance in a security group from a source outside of that group, you need to create an inbound rule.

diff --git a/docs/dds/umn/dds_02_0022.html b/docs/dds/umn/dds_02_0022.html index f2af50351..ee1c662da 100644 --- a/docs/dds/umn/dds_02_0022.html +++ b/docs/dds/umn/dds_02_0022.html @@ -1,7 +1,7 @@

Setting a Security Group

-

Scenarios

This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.

+

Scenarios

This section explains how to add a security group rule to control access to and from the DDS DB instances associated with a security group.DDS is compatible with MongoDB.

Precautions

The default security group rule allows all outgoing data packets. ECSs and DDS DB instances in the same security group can access each other. After a security group is created, you can create different rules for that security group, which allows you to control access to the DB instances that are in it.

To access a DB instance in a security group from a source outside of that group, you need to create an inbound rule.

diff --git a/docs/dds/umn/dds_02_0023.html b/docs/dds/umn/dds_02_0023.html index d43e3be2e..e1475e9bb 100644 --- a/docs/dds/umn/dds_02_0023.html +++ b/docs/dds/umn/dds_02_0023.html @@ -50,7 +50,7 @@
@@ -62,7 +62,7 @@ diff --git a/docs/dds/umn/dds_02_0028.html b/docs/dds/umn/dds_02_0028.html index 4bdc1ff91..4880a8472 100644 --- a/docs/dds/umn/dds_02_0028.html +++ b/docs/dds/umn/dds_02_0028.html @@ -1,7 +1,7 @@

Connecting to a Single Node Instance Over Private Networks

-

Scenarios

This section describes how to connect to a single-node instance using the MongoDB client over private networks.

+

Scenarios

This section describes how to connect to a single-node instance using the MongoDB client over private networks.DDS is compatible with MongoDB.

The MongoDB client can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.

Different OS scenarios: Examples include Linux and Windows clients.

diff --git a/docs/dds/umn/dds_02_0046.html b/docs/dds/umn/dds_02_0046.html index a08cadc1d..9eab7e195 100644 --- a/docs/dds/umn/dds_02_0046.html +++ b/docs/dds/umn/dds_02_0046.html @@ -3,13 +3,13 @@

Binding an EIP

Scenarios

After you create a DB instance, you can bind it to an EIP to allow external access. If you want to prohibit external access later, you can also unbind the EIP from the DB instance.

-

Precautions

  • Before accessing a database, you need to apply for an EIP on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section Setting a Security Group.
  • In the cluster instance, only mongos can be bound to an EIP. To change the EIP that has been bound to a node, you need to unbind it from the node first.
+

Precautions

  • Before accessing a database, you need to apply for an EIP on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see section Setting a Security Group.
  • In the cluster instance, only dds mongos can be bound to an EIP. To change the EIP that has been bound to a node, you need to unbind it from the node first.
-

Binding an EIP

  1. On the Instance Management page, click the target cluster instance.
  2. In the navigation pane on the left, choose Connections. In the Basic Information area, locate the target mongos node and click Bind EIP in the Operation column.

    Or in the Node Information area on the Basic Information page, locate the target mongos node and choose More > Bind EIP in the Operation column.

    -

  3. In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
  4. In the EIP column on the mongos tab, view the EIP that is successfully bound.

    To unbind an EIP from the DB instance, see Unbinding an EIP.

    +

    Binding an EIP

    1. On the Instance Management page, click the target cluster instance.
    2. In the navigation pane on the left, choose Connections. In the Basic Information area, locate the target dds mongos node and click Bind EIP in the Operation column.

      Or in the Node Information area on the Basic Information page, locate the target dds mongos node and choose More > Bind EIP in the Operation column.

      +

    3. In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
    4. In the EIP column on the dds mongos tab, view the EIP that is successfully bound.

      To unbind an EIP from the DB instance, see Unbinding an EIP.

    -

    Unbinding an EIP

    1. On the Instance Management page, click the target cluster instance.
    2. In the navigation pane on the left, choose Connections. In the Basic Information area, locate the target mongos node and click Unbind EIP in the Operation column.

      Or in the Node Information area on the Basic Information page, locate the target mongos node and choose More > Unbind EIP in the Operation column.

      +

      Unbinding an EIP

      1. On the Instance Management page, click the target cluster instance.
      2. In the navigation pane on the left, choose Connections. In the Basic Information area, locate the target dds mongos node and click Unbind EIP in the Operation column.

        Or in the Node Information area on the Basic Information page, locate the target dds mongos node and choose More > Unbind EIP in the Operation column.

      3. In the displayed dialog box, click Yes.

        To bind an EIP to the DB instance again, see Binding an EIP.

      diff --git a/docs/dds/umn/dds_02_0047.html b/docs/dds/umn/dds_02_0047.html index 65c5acf97..272ce2004 100644 --- a/docs/dds/umn/dds_02_0047.html +++ b/docs/dds/umn/dds_02_0047.html @@ -1,7 +1,7 @@

      Connecting to a Replica Set Instance Over Public Networks

      -

      Scenarios

      This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.

      +

      Scenarios

      This section describes how to connect to a replica set instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.

      You can directly perform operations on the primary and secondary nodes. Primary nodes are used for processing read and write requests. Secondary nodes replicate data from the primary and are used for processing read requests only.

      The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.

      Different OS scenarios: Examples include Linux and Windows clients.

      diff --git a/docs/dds/umn/dds_02_0048.html b/docs/dds/umn/dds_02_0048.html index 72a6171fa..f5ff69540 100644 --- a/docs/dds/umn/dds_02_0048.html +++ b/docs/dds/umn/dds_02_0048.html @@ -1,7 +1,7 @@

      Connecting to a Single Node Instance Over Public Networks

      -

      Scenarios

      This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.

      +

      Scenarios

      This section describes how to connect to a single-node instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.

      The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.

      Different OS scenarios: Examples include Linux and Windows clients.

      diff --git a/docs/dds/umn/dds_02_0052.html b/docs/dds/umn/dds_02_0052.html index 35beef17b..142004a69 100644 --- a/docs/dds/umn/dds_02_0052.html +++ b/docs/dds/umn/dds_02_0052.html @@ -50,7 +50,7 @@
@@ -64,7 +64,7 @@ diff --git a/docs/dds/umn/dds_02_0079.html b/docs/dds/umn/dds_02_0079.html index dae186990..005615fbc 100644 --- a/docs/dds/umn/dds_02_0079.html +++ b/docs/dds/umn/dds_02_0079.html @@ -50,7 +50,7 @@ @@ -62,7 +62,7 @@ diff --git a/docs/dds/umn/dds_02_0100.html b/docs/dds/umn/dds_02_0100.html index 3c3b663f3..50e18c79f 100644 --- a/docs/dds/umn/dds_02_0100.html +++ b/docs/dds/umn/dds_02_0100.html @@ -1,7 +1,7 @@

Enabling IP Addresses of shard and config Nodes

-

Scenarios

A cluster instance of Community Edition consists of mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to the mongos node. In certain scenarios, you need to read data from the shard or config node. Therefore, obtaining the IP address of the corresponding node is necessary.

+

Scenarios

A cluster instance of Community Edition consists of dds mongos, shard, and config nodes. When your services need to read and write data from and into databases, connect to the dds mongos node. In certain scenarios, you need to read data from the shard or config node. Therefore, obtaining the IP address of the corresponding node is necessary.

This section describes how to obtain the IP addresses of the shard and config nodes.

Before You Start

diff --git a/docs/dds/umn/dds_03_0003.html b/docs/dds/umn/dds_03_0003.html index 1eff219c5..0af6d5747 100644 --- a/docs/dds/umn/dds_03_0003.html +++ b/docs/dds/umn/dds_03_0003.html @@ -10,7 +10,7 @@

  • In the displayed dialog box, click Yes.
  • View the restart status.

    1. On the Instance Management page, the instance status is Restarting.
    2. On the Basic Information page, all nodes of the cluster instance cannot be restarted.

    • -

    Restarting a Node (Cluster)

    1. Log in to the DDS console.
    2. On the Instance Management page, click the target cluster instance.
    3. In the Node Information area on the Basic Information page, click the mongos, shard, or config tab, locate the target node, and in the Operation column, click Restart.
    4. In the displayed dialog box, click Yes.
    5. View the node status.

      When one node status is Restarting, other nodes of the instance cannot be restarted.

      +

      Restarting a Node (Cluster)

      1. Log in to the DDS console.
      2. On the Instance Management page, click the target cluster instance.
      3. In the Node Information area on the Basic Information page, click the dds mongos, shard, or config tab, locate the target node, and in the Operation column, click Restart.
      4. In the displayed dialog box, click Yes.
      5. View the node status.

        When one node status is Restarting, other nodes of the instance cannot be restarted.

    diff --git a/docs/dds/umn/dds_03_0018.html b/docs/dds/umn/dds_03_0018.html index e78fa131f..f6ee1c998 100644 --- a/docs/dds/umn/dds_03_0018.html +++ b/docs/dds/umn/dds_03_0018.html @@ -6,7 +6,7 @@

    Reverting Nodes in Batches

    1. Log in to the DDS console.
    2. On the Instance Management page, locate the cluster instance to which nodes fail to be added and choose More > Revert in the Operation column.
    3. In the displayed dialog box, click Yes.

      During reversal, the instance status is Deleting node. This process takes about 1 to 3 minutes.

    -

    Deleting Failed Cluster Instance Nodes

    1. Log in to the DDS console.
    2. On the Instance Management page, click the target cluster instance to which the node fails to be added.
    3. In the Node Information area on the Basic Information tab, click the mongos or shard tab, locate the mongos or shard that failed to be added, and choose More > Delete.
    4. In the displayed dialog box, click Yes.

      During deletion, the node status is Deleting node. This process takes about 1 to 3 minutes.

      +

      Deleting Failed Cluster Instance Nodes

      1. Log in to the DDS console.
      2. On the Instance Management page, click the target cluster instance to which the node fails to be added.
      3. In the Node Information area on the Basic Information tab, click the dds mongos or shard tab, locate the dds mongos or shard that failed to be added, and choose More > Delete.
      4. In the displayed dialog box, click Yes.

        During deletion, the node status is Deleting node. This process takes about 1 to 3 minutes.

    diff --git a/docs/dds/umn/dds_03_0026.html b/docs/dds/umn/dds_03_0026.html index ac4093186..6f754bcd3 100644 --- a/docs/dds/umn/dds_03_0026.html +++ b/docs/dds/umn/dds_03_0026.html @@ -30,7 +30,7 @@
    @@ -45,7 +45,7 @@ @@ -60,7 +60,7 @@ @@ -75,7 +75,7 @@ @@ -90,7 +90,7 @@ @@ -105,7 +105,7 @@ @@ -316,7 +316,7 @@ @@ -331,7 +331,7 @@ @@ -346,7 +346,7 @@ @@ -361,7 +361,7 @@ @@ -376,7 +376,7 @@ @@ -391,7 +391,7 @@ @@ -406,7 +406,7 @@ @@ -698,7 +698,7 @@ @@ -712,7 +712,7 @@ @@ -729,7 +729,7 @@ @@ -744,7 +744,7 @@ @@ -879,7 +879,7 @@ @@ -903,7 +903,7 @@ - @@ -63,7 +63,7 @@ @@ -77,19 +77,19 @@ - - - - - - diff --git a/docs/dds/umn/en-us_topic_0044018334.html b/docs/dds/umn/en-us_topic_0044018334.html index b5e983a72..8c810059f 100644 --- a/docs/dds/umn/en-us_topic_0044018334.html +++ b/docs/dds/umn/en-us_topic_0044018334.html @@ -26,7 +26,7 @@ 
    Enter password:
  • Method 2: Using standard URI format.

    mongo mongodb://rwuser:<password>@<DB_HOST>:<DB_PORT>,<DB_HOST>:<DB_PORT>/test?authSource=admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

    The connection information can be obtained in the Address column on the Instance Management page.

    -

    A connection address indicates that one of the mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.

    +

    A connection address indicates that one of the dds mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.

    • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the Private IP Address column in the node list on the Connections page.
    • DB_PORT indicates the port number. Obtain the value from Database Port in the Basic Information area on the Connections page.
    • DB_HOST and DB_PORT can also be obtained from the Node Information area on the Basic Information page.
    • DB_USER indicates the database account name. The default value is rwuser.
    • <password> indicates the password of the database account. If the password contains at signs (@),exclamation marks (!), or percent signs (%), replace them with hexadecimal URL codes %40, %21, and %25 respectively.
    • If user inputs this command then the password will be stored in logfiles and can be found in linux history, and in process list. So please note that plaintext passwords are risky.
    • FILE_PATH indicates the path where the root certificate is stored.
    @@ -43,7 +43,7 @@ 
    Enter password:
  • Method 2: Using standard URI format

    mongo mongodb://rwuser:<password>@<DB_HOST1>:<DB_PORT1>,<DB_HOST2>:<DB_PORT2>/test?authSource=admin

    The connection information can be obtained in the Address column on the Instance Management page.

    -

    A connection address indicates that one of the mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.

    +

    A connection address indicates that one of the dds mongos nodes will be randomly connected. If you use this method to connect to a DB instance, use the MongoDB client of version later than 3.4.

    • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the Private IP Address column in the node list on the Connections page.
    • DB_PORT indicates the port number. Obtain the value from Database Port in the Basic Information area on the Connections page.
    • DB_HOST and DB_PORT can also be obtained from the Node Information area on the Basic Information page.
    • DB_USER indicates the database account name. The default value is rwuser.
    • <password> indicates the password of the database account. If the password contains at signs (@),exclamation marks (!), or percent signs (%), replace them with hexadecimal URL codes %40, %21, and %25 respectively.
    • If user inputs this command then the password will be stored in logfiles and can be found in linux history, and in process list. So please note that plaintext passwords are risky.
    diff --git a/docs/dds/umn/en-us_topic_0104472218.html b/docs/dds/umn/en-us_topic_0104472218.html index 5214307ec..58271ed79 100644 --- a/docs/dds/umn/en-us_topic_0104472218.html +++ b/docs/dds/umn/en-us_topic_0104472218.html @@ -1,7 +1,7 @@

    Changing a Cluster DB Instance Class

    -

    Changing mongos

    1. Log in to the DDS console.
    2. On the Instance Management page, click the target cluster instance.
    3. In the Node Information area on the Basic Information page, click the mongos tab, locate the target mongos, and click Change Instance Class in the Operation column.
    4. On the displayed page, select the new instance class and click Submit.
    5. View the DB instance class change result.

      • When the CPU or memory of a DB instance is being changed, the status displayed in the Status column is Changing instance class. This process takes up to 10 minutes.
      • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
      • In the Node Information area on the Basic Information page, click the mongos tab and view the new instance class.
      +

      Changing dds mongos

      1. Log in to the DDS console.
      2. On the Instance Management page, click the target cluster instance.
      3. In the Node Information area on the Basic Information page, click the dds mongos tab, locate the target dds mongos, and click Change Instance Class in the Operation column.
      4. On the displayed page, select the new instance class and click Submit.
      5. View the DB instance class change result.

        • When the CPU or memory of a DB instance is being changed, the status displayed in the Status column is Changing instance class. This process takes up to 10 minutes.
        • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
        • In the Node Information area on the Basic Information page, click the dds mongos tab and view the new instance class.

      Changing shard

      1. Log in to the DDS console.
      2. On the Instance Management page, click the target cluster instance.
      3. In the Node Information area on the Basic Information page, click the shard tab, locate the target shard, and click Change Instance Class in the Operation column.
      4. On the displayed page, select the new instance class and click Submit.
      5. View the DB instance class change result.

        • When the CPU or memory of a DB instance is being changed, the status displayed in the Status column is Changing instance class. This process takes up to 30 minutes.
        • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
        • Go to the Basic Information page of the cluster instance you scaled up, click the shard tab in the Node Information area, and view the new instance class.
        diff --git a/docs/dds/umn/en-us_topic_0105284966.html b/docs/dds/umn/en-us_topic_0105284966.html index 358d5d12e..1c1b9c5c2 100644 --- a/docs/dds/umn/en-us_topic_0105284966.html +++ b/docs/dds/umn/en-us_topic_0105284966.html @@ -1,7 +1,7 @@

        Connecting to a Replica Set Instance Over Private Networks

        -

        Scenarios

        This section describes how to connect to a replica set instance using the MongoDB client over private networks.

        +

        Scenarios

        This section describes how to connect to a replica set instance using the MongoDB client over private networks.DDS is compatible with MongoDB.

        You can directly perform operations on the primary and secondary nodes. Primary nodes are used for processing read and write requests. Secondary nodes replicate data from the primary and are used for processing read requests only.

        The MongoDB client can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.

        Different OS scenarios: The following uses Linux ECS and Window client as an example.

        diff --git a/docs/dds/umn/en-us_topic_error_log.html b/docs/dds/umn/en-us_topic_error_log.html index 091146357..0b7676b65 100644 --- a/docs/dds/umn/en-us_topic_error_log.html +++ b/docs/dds/umn/en-us_topic_error_log.html @@ -3,7 +3,7 @@

        Error Log

        Scenarios

        DDS log management allows you to view database-level logs, including warning- and error-level logs generated during database running, which help you analyze system problems.

        -

        Procedure

        1. Log in to the DDS console.
        2. On the Instance Management page, click the target DB instance.
        3. In the navigation pane on the left, click Error Logs.
        4. On the displayed page, click Error Logs. Then, view the log details.

          • For a cluster instance, you can view error logs of the mongos, shard, and config nodes.
          • For a replica set instance, you can view the error logs of the primary, secondary, and hidden nodes.
          • For a single node instance, you can view error logs of the current node.
          • You can view up to 2,000 error logs of a specified node type, at a specified level, and within a specified period.
          +

          Procedure

          1. Log in to the DDS console.
          2. On the Instance Management page, click the target DB instance.
          3. In the navigation pane on the left, click Error Logs.
          4. On the displayed page, click Error Logs. Then, view the log details.

            • For a cluster instance, you can view error logs of the dds mongos, shard, and config nodes.
            • For a replica set instance, you can view the error logs of the primary, secondary, and hidden nodes.
            • For a single node instance, you can view error logs of the current node.
            • You can view up to 2,000 error logs of a specified node type, at a specified level, and within a specified period.

        diff --git a/docs/dds/umn/en-us_topic_increase_nodes.html b/docs/dds/umn/en-us_topic_increase_nodes.html index 48feddd79..c195bcbeb 100644 --- a/docs/dds/umn/en-us_topic_increase_nodes.html +++ b/docs/dds/umn/en-us_topic_increase_nodes.html @@ -3,10 +3,10 @@

        Adding Nodes to a Cluster

        Scenarios

        This section describes how to add nodes to a cluster instance.

        -
        • You can add nodes when the instance status is Available, Deleting backup, or Checking restoration.
        • A DB instance cannot be deleted when nodes are being added.
        • Mongos and shard nodes that are successfully added cannot be deleted.
        +
        • You can add nodes when the instance status is Available, Deleting backup, or Checking restoration.
        • A DB instance cannot be deleted when nodes are being added.
        • dds mongos and shard nodes that are successfully added cannot be deleted.
        -

        Add mongos

        1. Log in to the DDS console.
        2. On the Instance Management page, click the target cluster instance.
        3. On the mongos tab in the Node Information area, click Add mongos.
        4. On the displayed page, specify Node Class, Nodes, and Parameter Template and click Submit.

          A cluster instance of Community Edition supports up to 32 mongos nodes.

          -

        5. View the result of adding nodes.

          • This process takes up to 15 minutes. The status of the DB instance in the instance list is Adding node.
          • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
          • On the mongos tab in the Node Information area, view the information about the node you added.
          • If the mongos fail to be added, you can revert them in batches or delete them one by one. For details, see section Reverting and Deleting Failed Cluster Instance Nodes.
          +

          Add dds mongos

          1. Log in to the DDS console.
          2. On the Instance Management page, click the target cluster instance.
          3. On the dds mongos tab in the Node Information area, click Add dds mongos.
          4. On the displayed page, specify Node Class, Nodes, and Parameter Template and click Submit.

            A cluster instance of Community Edition supports up to 32 dds mongos nodes.

            +

          5. View the result of adding nodes.

            • This process takes up to 15 minutes. The status of the DB instance in the instance list is Adding node.
            • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
            • On the dds mongos tab in the Node Information area, view the information about the node you added.
            • If the dds mongos fail to be added, you can revert them in batches or delete them one by one. For details, see section Reverting and Deleting Failed Cluster Instance Nodes.

          Add shard

          1. Log in to the DDS console.
          2. On the Instance Management page, click the target cluster instance.
          3. On the shard tab in the Node Information area, click Add shard.
          4. Specify Node Class, Storage Space, Nodes, and Parameter Template and click Submit.

            • The storage space you applied for will contain the system overhead. The storage space can be configured from 10 GB to 2000 GB and must be an integer multiple of 10.
            • A cluster instance of Community Edition supports up to 32 shard nodes.
            diff --git a/docs/dds/umn/en-us_topic_introduction.html b/docs/dds/umn/en-us_topic_introduction.html index df3686388..ef5c75297 100644 --- a/docs/dds/umn/en-us_topic_introduction.html +++ b/docs/dds/umn/en-us_topic_introduction.html @@ -3,7 +3,7 @@

            What Is DDS?

            Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB community version 4.0.3 as baseline version.It provides functions such as one-click deployment, elastic capacity expansion, disaster recovery, backup, restoration, monitoring, and alarm reporting.

            DDS has the following features:

            -
            • DDS automatically establishes the three-node replica set architecture. It supports fast deployment, high availability (HA) data storage, data redundancy, and failover.
            • DDS provides sharded cluster instances comprised of a config node paired with multiple shards and mongos nodes. These clusters can be easily scaled up to enhance read and write performance.
            • DDS lets you back up or restore a database from the management console in just a few clicks.
            • DDS provides performance metrics and you can configure alarm notifications to make it easier to keep abreast of instance statuses.
            +
            • DDS automatically establishes the three-node replica set architecture. It supports fast deployment, high availability (HA) data storage, data redundancy, and failover.
            • DDS provides sharded cluster instances comprised of a config node paired with multiple shards and dds mongos nodes. These clusters can be easily scaled up to enhance read and write performance.
            • DDS lets you back up or restore a database from the management console in just a few clicks.
            • DDS provides performance metrics and you can configure alarm notifications to make it easier to keep abreast of instance statuses.

            For details about the compatible DB engines and versions, see Database Engine and Version.

    Table 2 shard and mongos specifications

    vCPUs

    +
    @@ -80,9 +80,9 @@
    Table 2 shard and dds mongos specifications

    vCPUs

    Memory (GB)
    -

    Replica Set

    The specifications supported by a replica set are the same as those supported by shard and mongos. For details, see Table 2.

    +

    Replica Set

    The specifications supported by a replica set are the same as those supported by shard and dds mongos. For details, see Table 2.

    -

    Single Node

    The specifications supported by a single node are the same as those supported by shard and mongos. For details, see Table 2.

    +

    Single Node

    The specifications supported by a single node are the same as those supported by shard and dds mongos. For details, see Table 2.

    diff --git a/docs/dds/umn/dds_01_0026.html b/docs/dds/umn/dds_01_0026.html index b87231b82..4c529cbd6 100644 --- a/docs/dds/umn/dds_01_0026.html +++ b/docs/dds/umn/dds_01_0026.html @@ -45,7 +45,7 @@

    Adding node

    shard or mongos nodes are being added to a DDS cluster instance.

    +

    shard or dds mongos nodes are being added to a DDS cluster instance.

    Deleting node

    diff --git a/docs/dds/umn/dds_02_0006.html b/docs/dds/umn/dds_02_0006.html index d95dc95f7..7b7d49805 100644 --- a/docs/dds/umn/dds_02_0006.html +++ b/docs/dds/umn/dds_02_0006.html @@ -1,7 +1,7 @@

    Connecting to a Cluster Instance Over Public Networks

    -

    Scenarios

    This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.

    +

    Scenarios

    This section describes how to connect to a cluster instance using the MongoDB client and Robo 3T over public networks.DDS is compatible with MongoDB.

    The MongoDB client and Robo 3T can connect to a DB instance with an unencrypted connection or an encrypted connection (SSL). To improve data transmission security, you are advised to connect to DB instances using the SSL connection.

    Different OS scenarios: Examples include Linux and Windows clients.

    diff --git a/docs/dds/umn/dds_02_0012.html b/docs/dds/umn/dds_02_0012.html index 2adb8fede..75bf103df 100644 --- a/docs/dds/umn/dds_02_0012.html +++ b/docs/dds/umn/dds_02_0012.html @@ -50,7 +50,7 @@

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.
    • Disabled: Disable the encryption function.
    • Enabled: Enable encryption. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

    -
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
    +
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • Backups of replica sets are physical backups. If disk encryption is enabled, backup data will be encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    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: dds mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.

    Compatible MongoDB Version

    @@ -50,7 +50,7 @@

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.
    • Disabled: Disable the encryption function.
    • Enabled: Enable encryption. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

    -
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
    +
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • Backups of cluster instances are physical backups. If disk encryption is enabled, backup data will be encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    mongos node class

    +

    dds mongos node class

    For details about the mongos CPU and memory, see section DB Instance Specifications. After a DB instance is created, you can change its CPU and memory. For details, see section Changing a Cluster DB Instance Class.

    +

    For details about the dds mongos CPU and memory, see section DB Instance Specifications. After a DB instance is created, you can change its CPU and memory. For details, see section Changing a Cluster DB Instance Class.

    mongos nodes

    +

    dds mongos nodes

    The number of mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add mongos nodes if necessary. For details, see section Adding Nodes to a Cluster.

    +

    The number of dds mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add dds mongos nodes if necessary. For details, see section Adding Nodes to a Cluster.

    mongos parameter template

    +

    dds mongos parameter template

    The parameters that apply to the mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.

    +

    The parameters that apply to the dds mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.

    For details, see Modifying a Parameter Template.

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.

    Disk Encryption
    • Disabled: Disable the encryption function.
    • Enabled: Enable the encryption function. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

      -
      NOTE:
      • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
      • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
      • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      NOTE:
      • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
      • The backup of a single-node instance is a logical backup. Enabling disk encryption will not encrypt the backup data.
      • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
      • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.
    • Disabled: Disable the encryption function.
    • Enabled: Enable encryption. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

    -
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
    +
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • Backups of replica sets are physical backups. If disk encryption is enabled, backup data will be encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.

    Disk Encryption
    • Disabled: Disable the encryption function.
    • Enabled: Enable the encryption function. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

      -
      NOTE:
      • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
      • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
      • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      NOTE:
      • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
      • The backup of a single-node instance is a logical backup. Enabling disk encryption will not encrypt the backup data.
      • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
      • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • DDS DB instance
    • mongos node
    • Primary node
    • Secondary node
    +
    • DDS DB instance
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: database

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: ECS

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    0–1

    Monitored object: ECS

    -
    Monitored object type:
    • mongos node
    +
    Monitored object type:
    • dds mongos node
    • Primary node
    • Secondary node

    Monitored object: ECS

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: ECS

    Monitored object type:

    -
    • mongos node
    • Primary node
    • Secondary node
    +
    • dds mongos node
    • Primary node
    • Secondary node

    1 minute

    Monitored object: ECS

    Monitored object type:

    -
    • mongos node
    • Secondary node
    +
    • dds mongos node
    • Secondary node

    1 minute

    mongos_instance_id

    mongos node ID

    +

    DDS node ID

    mongod_primary_instance_id

    diff --git a/docs/dds/umn/dds_03_0040.html b/docs/dds/umn/dds_03_0040.html index 8c98c0c9a..26eda685f 100644 --- a/docs/dds/umn/dds_03_0040.html +++ b/docs/dds/umn/dds_03_0040.html @@ -3,7 +3,7 @@

    Task Center

    Scenarios

    This section describes how to view the progress and result of asynchronous tasks on the Task Center page.

    -

    Tasks Overview

    • Creating a snapshot backup
    • Creating a cluster Instance
    • Creating a replica set instance
    • Creating a single node instance
    • Scaling up storage space
    • Changing the Community Edition instance
    • Adding nodes
    • Adding standby nodes to a replica set
    • Restarting a cluster instance
    • Restarting cluster nodes
    • Restart a cluster node
    • Restarting a replica set instance
    • Restarting a single-node instance
    • Switch Primary and Secondary Nodes
    • Change Private IP Address
    • Changing a security group
    • Changing a database port
    • Bind EIP
    • Change AZ
    • Enabling the shard/config IP address
    • Modifying the oplog size
    • Restoring to a new cluster instance
    • Restoring to a new replica set instance
    • Restoring to a new single-node instance
    • Restoring a replica set instance to a point in time
    • Creating a physical backup
    • Creating a snapshot backup
    • Restore Database and Table
    +

    Tasks Overview

    • Creating a cluster Instance
    • Creating a replica set instance
    • Creating a single node instance
    • Scaling up storage space
    • Scaling down storage space
    • Changing the Community Edition instance class
    • Changing the Enhanced Edition instance class
    • Adding nodes
    • Restarting a cluster instance
    • Restarting cluster nodes
    • Restart a node
    • Restarting a replica set instance
    • Restarting a single-node instance
    • Restoring to a new cluster instance
    • Restoring to a new replica set instance
    • Restoring to a new single-node instance
    • Restoring a cluster instance to a point in time
    • Restoring a replica set instance to a point in time
    • Restoring a single-node instance to a point in time
    • Adding standby nodes to a replica set
    • Switch Primary and Secondary Nodes
    • Change Private IP Address
    • Changing a security group
    • Changing a database port
    • Bind EIP
    • Unbind EIP
    • Switch SSL
    • Change AZ
    • Enabling the shard/config IP address
    • Modifying the oplog size
    • Creating a physical backup
    • Creating a snapshot backup
    • Restoring data
    • Restoring data to a point in time
    • Restore database and tables
    • Restoring to the original instance
    • Restoring to a new instance
    • Restoring to the original instance to a specific point in time
    • Restoring to a new instance to a specific point in time
    • Recycling backups
    • Installing database patches
    • Adding read replicas
    • Deleting read replicas from a replica set instance

    Tasks that fail to be executed will be retained for seven days by default.

    diff --git a/docs/dds/umn/dds_03_0042.html b/docs/dds/umn/dds_03_0042.html index 9abe6e09b..b7fc7ec86 100644 --- a/docs/dds/umn/dds_03_0042.html +++ b/docs/dds/umn/dds_03_0042.html @@ -6,7 +6,7 @@

    Restoration Precautions

    • When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.

    Method 1

    1. Log in to the DDS console.
    2. On the Instance Management page, click the target cluster instance.
    3. In the navigation pane on the left, click Backups & Restorations.
    4. On the Backups & Restorations page, locate the target backup and click Restore in the Operation column.
    5. Select either of the following restoration methods and click OK.

      • Create New Instance

        The Create New Instance page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.

        -
        • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
        • The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
        • The storage space is the same as that of the original instance by default. You can only increase the storage space.
        • Other settings have default values and can be modified. For details, see section Creating a Cluster Instance.
        +
        • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
        • The number of dds mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
        • The storage space is the same as that of the original instance by default. You can only increase the storage space.
        • Other settings have default values and can be modified. For details, see section Creating a Cluster Instance.
      • Restore to Original
        • Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.
        • The administrator password of the database instance remains unchanged after the restoration.
        • If IP address is enabled both for the shards and config, the related password has to be changed for both of them.
      @@ -15,7 +15,7 @@

      Method 2

      1. Log in to the DDS console.
      2. In the navigation pane on the left, click Backup Management.
      3. On the Backup Management page, locate the target backup on the Clusters tab and click Restore in the Operation column.

        • If you use an automated backup, go to 4.
        • If you use a manual backup, check whether the original instance of the manual backup exists:
          • If so, then go to 4.
          • If not, then you can only restore the backup to a new DB instance. Go to Create New Instance step under 4.

      4. Select either of the following restoration methods and click OK.

        • Create New Instance

          The Create New Instance page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.

          -
          • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
          • The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
          • The storage space is the same as that of the original instance by default. You can only increase the storage space.
          • Other settings have default values and can be modified. For details, see section Creating a Cluster Instance.
          +
          • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
          • The number of dds mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
          • The storage space is the same as that of the original instance by default. You can only increase the storage space.
          • Other settings have default values and can be modified. For details, see section Creating a Cluster Instance.
        • Restore to Original
          • Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.
          • The administrator password of the database instance remains unchanged after the restoration.
          • If IP address is enabled both for the shards and config, the related password has to be changed for both of them.
        diff --git a/docs/dds/umn/dds_03_0052.html b/docs/dds/umn/dds_03_0052.html index cbf33e7c1..be469e2b0 100644 --- a/docs/dds/umn/dds_03_0052.html +++ b/docs/dds/umn/dds_03_0052.html @@ -2,6 +2,7 @@

        Migrating Data

        Scenarios

        DDS is accessible through an EIP in a public network or an ECS in a private network.

        +

        DDS is compatible with MongoDB.

        MongoDB can export data from a database into a JSON file. Such a JSON file can then be used to import the data to MongoDB databases. This section describes how to import the data from the JSON files to DDS using the mongoimport tool on the ECS or from some other devices that can access DDS.

        Prerequisites

        1. An ECS or a device that can access DDS is ready for use.
          • To connect your DDS DB instance through a private network:

            Create and log in to an ECS. For details, see "Creating and Logging In to a Windows ECS" or "Creating and Logging In to a Linux ECS" in the Elastic Cloud Server User Guide.

            @@ -18,7 +19,7 @@

            Enter the database administrator password when prompted:

            Enter password:

            The following is an example. After the command is executed, the exportfile.json file will be generated:

            -

            mongoexport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --out /tmp/mongodb/export/exportfile.json

            +

            mongoexport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --out /tmp/***/export/exportfile.json

          • Check the result.

            If information similar to the following is displayed, the data is successfully exported. x indicates the number of exported data records.

            exported x records

          • Compress the exported .json file.

            gzip exportfile.json

            @@ -36,7 +37,7 @@

            Enter the database administrator password when prompted:

            Enter password:

            The following is an example:

            -

            mongoimport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --file /tmp/mongodb/export/exportfile.json

            +

            mongoimport --host 192.168.1.21 --port 8635 --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase admin -u rwuser --db test02 --collection Test --file /tmp/***/export/exportfile.json

          • Check the result.

            If information similar to the following is displayed, the data is successfully imported. x indicates the number of imported data records.

            imported x records

        diff --git a/docs/dds/umn/dds_change_history.html b/docs/dds/umn/dds_change_history.html index f64642c75..7456398f3 100644 --- a/docs/dds/umn/dds_change_history.html +++ b/docs/dds/umn/dds_change_history.html @@ -36,7 +36,7 @@

    2022-03-29

    Modified the following content:

    - +

    2022-03-22

    @@ -82,7 +82,7 @@

    2020-10-15

    Modified the following content:

    - +

    2019-11-07

    @@ -182,7 +182,7 @@

    Added the following content:

    Modified the following content:

    - +

    2018-07-03

    diff --git a/docs/dds/umn/dds_faq_0012.html b/docs/dds/umn/dds_faq_0012.html index da7a71d85..15bd16687 100644 --- a/docs/dds/umn/dds_faq_0012.html +++ b/docs/dds/umn/dds_faq_0012.html @@ -2,7 +2,7 @@

    What Is the Number of DDS Database Connections?

    The number of connections indicates the number of applications that can be simultaneously connected to the database. The number of connections is irrelevant to the maximum number of users allowed by your applications or websites.

    -
    • For a cluster instance, the number of connections indicates the number of connections between the client and the mongos.
    • For a replica set instance, the number of connections indicates the number of connections between the client and the primary and secondary nodes.
    • For a single-node instance, the number of connections indicates the number of connections between the client and the node.
    +
    • For a cluster instance, the number of connections indicates the number of connections between the client and the dds mongos.
    • For a replica set instance, the number of connections indicates the number of connections between the client and the primary and secondary nodes.
    • For a single-node instance, the number of connections indicates the number of connections between the client and the node.
    diff --git a/docs/dds/umn/en-us_image_0000001096133880.png b/docs/dds/umn/en-us_image_0000001096133880.png deleted file mode 100644 index 6e7b2ff9d..000000000 Binary files a/docs/dds/umn/en-us_image_0000001096133880.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0000001142773903.png b/docs/dds/umn/en-us_image_0000001142773903.png index 4079a9b09..4b4c26e1d 100644 Binary files a/docs/dds/umn/en-us_image_0000001142773903.png and b/docs/dds/umn/en-us_image_0000001142773903.png differ diff --git a/docs/dds/umn/en-us_image_0000001142773909.png b/docs/dds/umn/en-us_image_0000001142773909.png index 4079a9b09..4d730c27d 100644 Binary files a/docs/dds/umn/en-us_image_0000001142773909.png and b/docs/dds/umn/en-us_image_0000001142773909.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133835.png b/docs/dds/umn/en-us_image_0000001143133835.png index 4079a9b09..180fcc155 100644 Binary files a/docs/dds/umn/en-us_image_0000001143133835.png and b/docs/dds/umn/en-us_image_0000001143133835.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133849.png b/docs/dds/umn/en-us_image_0000001143133849.png deleted file mode 100644 index 57c07999d..000000000 Binary files a/docs/dds/umn/en-us_image_0000001143133849.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0000001845343652.png b/docs/dds/umn/en-us_image_0000001845343652.png new file mode 100644 index 000000000..fd3c42d78 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001845343652.png differ diff --git a/docs/dds/umn/en-us_image_0000001891581965.png b/docs/dds/umn/en-us_image_0000001891581965.png new file mode 100644 index 000000000..7e636a40c Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001891581965.png differ diff --git a/docs/dds/umn/en-us_topic_0044018333.html b/docs/dds/umn/en-us_topic_0044018333.html index 84bc25d7f..66376b00a 100644 --- a/docs/dds/umn/en-us_topic_0044018333.html +++ b/docs/dds/umn/en-us_topic_0044018333.html @@ -34,7 +34,7 @@

    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: dds mongos, shard, and config. Each shard and config is a three-node replica set to ensure high availability.

    Compatible MongoDB Version

    @@ -50,7 +50,7 @@

    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.

      +
    • 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 DDS and is suitable for scenarios with a large number of write operations.
    • Disabled: Disable the encryption function.
    • Enabled: Enable encryption. This feature improves data security but slightly affects read/write performance.

      Key Name: Select or create a private key, which is the tenant key.

    -
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
    +
    NOTE:
    • After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is encrypted.
    • Backups of cluster instances are physical backups. If disk encryption is enabled, backup data will be encrypted.
    • To check whether the disk is encrypted, you can view Disk Encrypted in the DB instance list.
    • If disk encryption or backup data encryption is enabled, keep the key properly. Once the key is disabled, deleted, or frozen, the database will be unavailable and data may not be restored.
    • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.

    mongos node class

    +

    dds mongos node class

    For details about the mongos CPU and memory, see section DB Instance Specifications. After a DB instance is created, you can change its CPU and memory. For details, see section Changing a Cluster DB Instance Class.

    +

    For details about the dds mongos CPU and memory, see section DB Instance Specifications. After a DB instance is created, you can change its CPU and memory. For details, see section Changing a Cluster DB Instance Class.

    mongos nodes

    +

    dds mongos nodes

    The number of mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add mongos nodes if necessary. For details, see section Adding Nodes to a Cluster.

    +

    The number of dds mongos nodes. The value ranges from 2 to 32. After a DB instance is created, you can add dds mongos nodes if necessary. For details, see section Adding Nodes to a Cluster.

    mongos parameter template

    +

    dds mongos parameter template

    The parameters that apply to the mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.

    +

    The parameters that apply to the dds mongos nodes. After a DB instance is created, you can change the parameter template of a node to bring out the best performance.

    For details, see Modifying a Parameter Template.