diff --git a/docs/dds/umn/ALL_META.TXT.json b/docs/dds/umn/ALL_META.TXT.json index 0891cb36e..e8fc9f60d 100644 --- a/docs/dds/umn/ALL_META.TXT.json +++ b/docs/dds/umn/ALL_META.TXT.json @@ -13,9 +13,9 @@ "uri":"en-us_topic_introduction.html", "product_code":"dds", "code":"2", - "des":"Document Database Service (DDS) is compatible with MongoDB and is secure, highly available, reliable, scalable, and easy to use. It provides DB instance creation, scaling", + "des":"Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB. It provides functions such", "doc_type":"usermanual", - "kw":"MongoDB,scalable,scaling,redundancy,replica set,high availability (HA) data storage,redundancy,distr", + "kw":"elastic capacity expansion,disaster recovery,replica set,high availability (HA) data storage,data re", "title":"What Is DDS?", "githuburl":"" }, @@ -33,26 +33,36 @@ "uri":"dds_01_0011.html", "product_code":"dds", "code":"4", - "des":"Each DDS cluster is an independent document database. A sharded cluster consists of mongos, config, and shard.Data read and write requests are forwarded by mongos. A mong", + "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", "doc_type":"usermanual", - "kw":"Cluster Architecture,System Architecture,User Guide", - "title":"Cluster Architecture", + "kw":"Cluster,System Architecture,User Guide", + "title":"Cluster", "githuburl":"" }, { "uri":"dds_01_0012.html", "product_code":"dds", "code":"5", - "des":"A replica set consists of a set of mongod processes and provides a collection of data nodes to ensure data redundancy and reliability.For details about the mongod process", + "des":"A replica set consists of a set of mongod processes. It is a collection of nodes that help ensure data redundancy and reliability.For details about the mongod process, se", "doc_type":"usermanual", - "kw":"Replica Set Architecture,System Architecture,User Guide", - "title":"Replica Set Architecture", + "kw":"Replica Set,System Architecture,User Guide", + "title":"Replica Set", + "githuburl":"" + }, + { + "uri":"dds_01_0025.html", + "product_code":"dds", + "code":"6", + "des":"A single node instance, as its name suggests, contains only one node which can be accessed directly.As a supplement to the cluster and replica set architectures, the sing", + "doc_type":"usermanual", + "kw":"Single Node Architecture,System Architecture,User Guide", + "title":"Single Node Architecture", "githuburl":"" }, { "uri":"dds_01_0001.html", "product_code":"dds", - "code":"6", + "code":"7", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Basic Concepts", @@ -62,8 +72,8 @@ { "uri":"dds_01_0002.html", "product_code":"dds", - "code":"7", - "des":"DDS cluster instances consist of mongos, config, and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and writing data, pr", + "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", "doc_type":"usermanual", "kw":"Cluster,Basic Concepts,User Guide", "title":"Cluster", @@ -72,17 +82,17 @@ { "uri":"dds_01_0005.html", "product_code":"dds", - "code":"8", - "des":"A database parameter group is a collection of configuration parameters and values and can be applied to multiple DB instances.", + "code":"9", + "des":"A database parameter template is a collection of configuration parameters and values and can be applied to multiple DB instances.", "doc_type":"usermanual", - "kw":"Database Parameter Group,Basic Concepts,User Guide", - "title":"Database Parameter Group", + "kw":"Database Parameter Template,Basic Concepts,User Guide", + "title":"Database Parameter Template", "githuburl":"" }, { "uri":"dds_01_0027.html", "product_code":"dds", - "code":"9", + "code":"10", "des":"A region is a geographic area in which resources used by DDS are located.Each region comprises one or more AZs and is completely isolated from other regions. AZs within t", "doc_type":"usermanual", "kw":"Regions and AZs,Basic Concepts,User Guide", @@ -92,57 +102,27 @@ { "uri":"dds_01_0006.html", "product_code":"dds", - "code":"10", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Product Advantages", - "title":"Product Advantages", - "githuburl":"" - }, - { - "uri":"dds_01_0007.html", - "product_code":"dds", "code":"11", - "des":"The three-node replica set architecture of DDS ensures high service availability.In a replica set, both the primary and secondary nodes provide services. If a primary nod", + "des":"DDS supports three deployment architectures: cluster, replica set, and single node. They meet requirements of different service scenarios.ClusterA cluster consists of thr", "doc_type":"usermanual", - "kw":"High Reliability,Product Advantages,User Guide", - "title":"High Reliability", + "kw":"NoSQL database,MongoDB,Functions and Features,Introduction,User Guide", + "title":"Functions and Features", "githuburl":"" }, { - "uri":"dds_01_0008.html", + "uri":"dds_01_0015.html", "product_code":"dds", "code":"12", - "des":"DDS uses Virtual Private Clouds (VPCs) and network security groups to isolate your DB instances. VPCs allow you to configure IP address ranges that are allowed access to ", + "des":"Game players' information generated from game applications, such as players' equipment and bonus points, are stored in DDS databases. During peak hours, DDS cluster insta", "doc_type":"usermanual", - "kw":"access to DDS,High Security,Product Advantages,User Guide", - "title":"High Security", - "githuburl":"" - }, - { - "uri":"dds_01_0010.html", - "product_code":"dds", - "code":"13", - "des":"You can create a DB instance on the management console and access DDS through an Elastic Cloud Server (ECS) to reduce the application response time. If you need to access", - "doc_type":"usermanual", - "kw":"NoSQL database,MongoDB,Ease of Use,Product Advantages,User Guide", - "title":"Ease of Use", - "githuburl":"" - }, - { - "uri":"dds_01_0009.html", - "product_code":"dds", - "code":"14", - "des":"DDS supports the cluster mode. You can select multiple mongos and shards. When your service changes or the current instance configuration cannot meet the application perf", - "doc_type":"usermanual", - "kw":"Scalability,Product Advantages,User Guide", - "title":"Scalability", + "kw":"Typical Application Scenarios,Introduction,User Guide", + "title":"Typical Application Scenarios", "githuburl":"" }, { "uri":"dds_01_0013.html", "product_code":"dds", - "code":"15", + "code":"13", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DDS DB Instance", @@ -152,8 +132,8 @@ { "uri":"dds_01_0024.html", "product_code":"dds", - "code":"16", - "des":"DB instance specifications are listed in the following table.DB instance specifications vary depending on the actual environment.For details about the cluster instance sp", + "code":"14", + "des":"DB instance specifications are listed in the following table.The DB instance specifications depend on service requirements.You can change the maximum number of connection", "doc_type":"usermanual", "kw":"DB Instance Specifications,DDS DB Instance,User Guide", "title":"DB Instance Specifications", @@ -162,8 +142,8 @@ { "uri":"dds_01_0014.html", "product_code":"dds", - "code":"17", - "des":"Currently, DDS is compatible with MongoDB 3.2 and 3.4 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.", + "code":"15", + "des":"DDS is compatible with MongoDB 3.2, 3.4, 4.0, and 4.2 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.", "doc_type":"usermanual", "kw":"Database Engine and Version,DDS DB Instance,User Guide", "title":"Database Engine and Version", @@ -172,57 +152,67 @@ { "uri":"dds_01_0026.html", "product_code":"dds", - "code":"18", + "code":"16", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Database Status,DDS DB Instance,User Guide", - "title":"Database Status", + "kw":"DB Instance Status,DDS DB Instance,User Guide", + "title":"DB Instance Status", "githuburl":"" }, { - "uri":"dds_01_0015.html", + "uri":"dds_01_0022.html", "product_code":"dds", - "code":"19", - "des":"Mobile Apps and MapsDDS supports two-dimensional space indexes for mobile applications (Apps) and maps that have location query requests. In addition, the dynamic storage", + "code":"17", + "des":"To improve the stability and security of DB instances, there are some constraints on the use of DDS. For details, see Table 1.", "doc_type":"usermanual", - "kw":"Typical Application Scenarios,Introduction,User Guide", - "title":"Typical Application Scenarios", - "githuburl":"" - }, - { - "uri":"dds_01_0016.html", - "product_code":"dds", - "code":"20", - "des":"ECS provides DDS with elastic computing resources. DDS needs to apply for resources from ECS to build a running environment for DB instances.For more information, see the", - "doc_type":"usermanual", - "kw":"Related Services,Introduction,User Guide", - "title":"Related Services", + "kw":"Constraints and Recommendations,Introduction,User Guide", + "title":"Constraints and Recommendations", "githuburl":"" }, { "uri":"dds_01_0017.html", "product_code":"dds", - "code":"21", - "des":"DDS provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and user gr", + "code":"18", + "des":"IAM provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and user gr", "doc_type":"usermanual", "kw":"User Permissions,Introduction,User Guide", "title":"User Permissions", "githuburl":"" }, + { + "uri":"dds_01_0019.html", + "product_code":"dds", + "code":"19", + "des":"If you need to assign different permissions to employees in your enterprise to access your DDS resources, IAM is a good choice for fine-grained permissions management. IA", + "doc_type":"usermanual", + "kw":"Permissions Management,Introduction,User Guide", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"dds_01_0016.html", + "product_code":"dds", + "code":"20", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Related Services,Introduction,User Guide", + "title":"Related Services", + "githuburl":"" + }, { "uri":"dds_02_0043.html", "product_code":"dds", - "code":"22", - "des":"You have registered an account.For the first time you use DDS, register an account at the official website. After the registration, your account has permissions to access", + "code":"21", + "des":"You have registered an account.For the first time you use DDS, apply for an account at the official website. After the application is successful, your account has permiss", "doc_type":"usermanual", - "kw":"Logging In to the DDS Console,User Guide", - "title":"Logging In to the DDS Console", + "kw":"Logging in to the DDS Console,User Guide", + "title":"Logging in to the DDS Console", "githuburl":"" }, { "uri":"dds_02_cluster.html", "product_code":"dds", - "code":"23", + "code":"22", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Getting Started with Clusters", @@ -230,89 +220,129 @@ "githuburl":"" }, { - "uri":"dds_02_0003.html", + "uri":"dds_02_0001.html", "product_code":"dds", - "code":"24", - "des":"This section describes how to create a cluster instance, set a security group, and connect to a cluster instance.Users who create the DDS DB instance for the first time.U", + "code":"23", + "des":"You can access DDS over private or public networks.", "doc_type":"usermanual", - "kw":"Service Process,Getting Started with Clusters,User Guide", - "title":"Service Process", - "githuburl":"" - }, - { - "uri":"dds_02_0002.html", - "product_code":"dds", - "code":"25", - "des":"To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.", - "doc_type":"usermanual", - "kw":"DDS DB instance,Restrictions,Getting Started with Clusters,User Guide", - "title":"Restrictions", - "githuburl":"" - }, - { - "uri":"dds_02_0008.html", - "product_code":"dds", - "code":"26", - "des":"This section describes how to create a DDS cluster instance of Community Edition on the DDS management console. DDS allows you to tailor your computing resources and stor", - "doc_type":"usermanual", - "kw":"DB instance,Creating a Cluster Instance,Getting Started with Clusters,User Guide", - "title":"Creating a Cluster Instance", - "githuburl":"" - }, - { - "uri":"dds_02_0005.html", - "product_code":"dds", - "code":"27", - "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.You can access a DDS DB instance in either ", - "doc_type":"usermanual", - "kw":"DDS DB instances,Setting a Security Group,Getting Started with Clusters,User Guide", - "title":"Setting a Security Group", + "kw":"Connection Methods,Getting Started with Clusters,User Guide", + "title":"Connection Methods", "githuburl":"" }, { "uri":"dds_02_0009.html", "product_code":"dds", - "code":"28", + "code":"24", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Connecting to a Cluster Instance", - "title":"Connecting to a Cluster Instance", + "kw":"Connecting to a Cluster Instance Over Private Networks", + "title":"Connecting to a Cluster Instance Over Private Networks", "githuburl":"" }, { - "uri":"dds_02_0006.html", + "uri":"dds_02_0010.html", "product_code":"dds", - "code":"29", - "des":"You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:Use a private IP address when:DDS provides a p", + "code":"25", + "des":"This section describes how to create a cluster instance on the management console, set a security group, and connect to a cluster instance over private networks.The follo", "doc_type":"usermanual", - "kw":"Binding and Unbinding an EIP,Connecting to a Cluster Instance,User Guide", - "title":"Binding and Unbinding an EIP", + "kw":"Overview,Connecting to a Cluster Instance Over Private Networks,User Guide", + "title":"Overview", "githuburl":"" }, { - "uri":"dds_02_0007.html", + "uri":"en-us_topic_0044018333.html", "product_code":"dds", - "code":"30", - "des":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a database using SSL. For details, see SSL Co", + "code":"26", + "des":"This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space", "doc_type":"usermanual", - "kw":"Enabling or Disabling SSL,Connecting to a Cluster Instance,User Guide", - "title":"Enabling or Disabling SSL", + "kw":"Creating a Cluster Instance,Connecting to a Cluster Instance Over Private Networks,User Guide", + "title":"Creating a Cluster Instance", + "githuburl":"" + }, + { + "uri":"dds_02_0022.html", + "product_code":"dds", + "code":"27", + "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", + "doc_type":"usermanual", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Private Networks,Use", + "title":"Setting a Security Group", "githuburl":"" }, { "uri":"en-us_topic_0044018334.html", "product_code":"dds", - "code":"31", - "des":"This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt ", + "code":"28", + "des":"This section describes how to connect to a cluster instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an unencry", "doc_type":"usermanual", - "kw":"DDS DB instance,DB instance,DB instance,Connecting to a DB Instance Through a Client,Connecting to a", - "title":"Connecting to a DB Instance Through a Client", + "kw":"DB instance,Connecting to a Cluster Instance Over Private Networks,Connecting to a Cluster Instance ", + "title":"Connecting to a Cluster Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0013.html", + "product_code":"dds", + "code":"29", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a Cluster Instance Over Public Networks", + "title":"Connecting to a Cluster Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0014.html", + "product_code":"dds", + "code":"30", + "des":"This section describes how to create a cluster instance on the management console, set a security group, bind an EIP, and connect to a cluster instance over public networ", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Cluster Instance Over Public Networks,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dds_02_0016.html", + "product_code":"dds", + "code":"31", + "des":"This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space", + "doc_type":"usermanual", + "kw":"Creating a Cluster Instance,Connecting to a Cluster Instance Over Public Networks,User Guide", + "title":"Creating a Cluster Instance", + "githuburl":"" + }, + { + "uri":"dds_02_0046.html", + "product_code":"dds", + "code":"32", + "des":"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", + "doc_type":"usermanual", + "kw":"Binding an EIP,Connecting to a Cluster Instance Over Public Networks,User Guide", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"dds_02_0019.html", + "product_code":"dds", + "code":"33", + "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", + "doc_type":"usermanual", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Cluster Instance Over Public Networks,User", + "title":"Setting a Security Group", + "githuburl":"" + }, + { + "uri":"dds_02_0006.html", + "product_code":"dds", + "code":"34", + "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", + "doc_type":"usermanual", + "kw":"DB instance,Connecting to a Cluster Instance Over Public Networks,Connecting to a Cluster Instance O", + "title":"Connecting to a Cluster Instance Over Public Networks", "githuburl":"" }, { "uri":"dds_02_replica_set.html", "product_code":"dds", - "code":"32", + "code":"35", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Getting Started with Replica Sets", @@ -320,179 +350,559 @@ "githuburl":"" }, { - "uri":"dds_02_0010.html", + "uri":"dds_02_0042.html", "product_code":"dds", - "code":"33", - "des":"This section describes how to create a replica set instance, set a security group, and connect to a replica set instance.Users who create the DDS DB instance for the firs", + "code":"36", + "des":"You can access DDS over private or public networks.", "doc_type":"usermanual", - "kw":"Service Process,Getting Started with Replica Sets,User Guide", - "title":"Service Process", + "kw":"Connection Methods,Getting Started with Replica Sets,User Guide", + "title":"Connection Methods", "githuburl":"" }, { - "uri":"dds_02_0011.html", + "uri":"dds_02_0055.html", "product_code":"dds", - "code":"34", - "des":"To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.", + "code":"37", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"DDS DB instance,Restrictions,Getting Started with Replica Sets,User Guide", - "title":"Restrictions", + "kw":"Connecting to a Replica Set Instance Over Private Networks", + "title":"Connecting to a Replica Set Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0057.html", + "product_code":"dds", + "code":"38", + "des":"This section describes how to create a replica set instance on the management console, set a security group, and connect to a replica set instance over private networks.T", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Replica Set Instance Over Private Networks,User Guide", + "title":"Overview", "githuburl":"" }, { "uri":"dds_02_0012.html", "product_code":"dds", - "code":"35", - "des":"This section describes how to create a DDS replica set instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your", + "code":"39", + "des":"This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your busin", "doc_type":"usermanual", - "kw":"DB instance,Creating a Replica Set Instance,Getting Started with Replica Sets,User Guide", + "kw":"DB instances,Creating a Replica Set Instance,Connecting to a Replica Set Instance Over Private Netwo", "title":"Creating a Replica Set Instance", "githuburl":"" }, { - "uri":"dds_02_0013.html", + "uri":"dds_02_0049.html", "product_code":"dds", - "code":"36", - "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group. This document describes how to set securit", + "code":"40", + "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how t", "doc_type":"usermanual", - "kw":"DDS DB instances,Setting a Security Group,Getting Started with Replica Sets,User Guide", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Replica Set Instance Over Private Networks", "title":"Setting a Security Group", "githuburl":"" }, - { - "uri":"dds_02_0014.html", - "product_code":"dds", - "code":"37", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Connecting to a Replica Set Instance", - "title":"Connecting to a Replica Set Instance", - "githuburl":"" - }, - { - "uri":"dds_02_0015.html", - "product_code":"dds", - "code":"38", - "des":"You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:Use a private IP address when:DDS provides a p", - "doc_type":"usermanual", - "kw":"Binding and Unbinding an EIP,Connecting to a Replica Set Instance,User Guide", - "title":"Binding and Unbinding an EIP", - "githuburl":"" - }, - { - "uri":"dds_02_0016.html", - "product_code":"dds", - "code":"39", - "des":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a database using SSL. For details, see SSL Co", - "doc_type":"usermanual", - "kw":"Enabling or Disabling SSL,Connecting to a Replica Set Instance,User Guide", - "title":"Enabling or Disabling SSL", - "githuburl":"" - }, { "uri":"en-us_topic_0105284966.html", "product_code":"dds", - "code":"40", - "des":"This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt ", + "code":"41", + "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", "doc_type":"usermanual", - "kw":"DDS DB instance,DB instance,DDS DB instance,DDS DB instance,Connecting to a DB Instance Through a Cl", - "title":"Connecting to a DB Instance Through a Client", + "kw":"DDS DB instance,DDS DB instance,Connecting to a Replica Set Instance Over Private Networks,Connectin", + "title":"Connecting to a Replica Set Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0050.html", + "product_code":"dds", + "code":"42", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a Replica Set Instance Over Public Networks", + "title":"Connecting to a Replica Set Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0051.html", + "product_code":"dds", + "code":"43", + "des":"This section describes how to create a replica set instance on the management console, set a security group, bind an EIP, and connect to a replica set instance over publi", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Replica Set Instance Over Public Networks,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dds_02_0052.html", + "product_code":"dds", + "code":"44", + "des":"This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your busin", + "doc_type":"usermanual", + "kw":"DB instances,Creating a Replica Set Instance,Connecting to a Replica Set Instance Over Public Networ", + "title":"Creating a Replica Set Instance", + "githuburl":"" + }, + { + "uri":"dds_02_0053.html", + "product_code":"dds", + "code":"45", + "des":"After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB", + "doc_type":"usermanual", + "kw":"Binding an EIP,Connecting to a Replica Set Instance Over Public Networks,User Guide", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"dds_02_0054.html", + "product_code":"dds", + "code":"46", + "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how t", + "doc_type":"usermanual", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Replica Set Instance Over Public Networks,", + "title":"Setting a Security Group", + "githuburl":"" + }, + { + "uri":"dds_02_0047.html", + "product_code":"dds", + "code":"47", + "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", + "doc_type":"usermanual", + "kw":"DDS DB instance,Connecting to a Replica Set Instance Over Public Networks,Connecting to a Replica Se", + "title":"Connecting to a Replica Set Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"dds_02_single_node.html", + "product_code":"dds", + "code":"48", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started with Single Nodes", + "title":"Getting Started with Single Nodes", + "githuburl":"" + }, + { + "uri":"dds_02_0070.html", + "product_code":"dds", + "code":"49", + "des":"You can access DDS over private or public networks.", + "doc_type":"usermanual", + "kw":"Connection Methods,Getting Started with Single Nodes,User Guide", + "title":"Connection Methods", + "githuburl":"" + }, + { + "uri":"dds_02_0074.html", + "product_code":"dds", + "code":"50", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a Single-Node Instance Over Private Networks", + "title":"Connecting to a Single-Node Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0075.html", + "product_code":"dds", + "code":"51", + "des":"This section describes how to create a single node instance on the management console, set a security group, and connect to a single node instance over private networks.T", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Single-Node Instance Over Private Networks,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dds_02_0023.html", + "product_code":"dds", + "code":"52", + "des":"This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your bus", + "doc_type":"usermanual", + "kw":"DB instances,Creating a Single Node Instance,Connecting to a Single-Node Instance Over Private Netwo", + "title":"Creating a Single Node Instance", + "githuburl":"" + }, + { + "uri":"dds_02_0024.html", + "product_code":"dds", + "code":"53", + "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.The default security group rule allows all ", + "doc_type":"usermanual", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Single-Node Instance Over Private Networks", + "title":"Setting a Security Group", + "githuburl":"" + }, + { + "uri":"dds_02_0028.html", + "product_code":"dds", + "code":"54", + "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", + "doc_type":"usermanual", + "kw":"DDS DB instance,DDS DB instance,Connecting to a Single Node Instance Over Private Networks,Connectin", + "title":"Connecting to a Single Node Instance Over Private Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0077.html", + "product_code":"dds", + "code":"55", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a Single Node Instance Over Public Networks", + "title":"Connecting to a Single Node Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"dds_02_0078.html", + "product_code":"dds", + "code":"56", + "des":"This section describes how to create a single node instance on the management console, set a security group, bind an EIP, and connect to a single node instance over publi", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a Single Node Instance Over Public Networks,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dds_02_0079.html", + "product_code":"dds", + "code":"57", + "des":"This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your bus", + "doc_type":"usermanual", + "kw":"DB instances,Creating a Single Node Instance,Connecting to a Single Node Instance Over Public Networ", + "title":"Creating a Single Node Instance", + "githuburl":"" + }, + { + "uri":"dds_02_0026.html", + "product_code":"dds", + "code":"58", + "des":"After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB", + "doc_type":"usermanual", + "kw":"Binding an EIP,Connecting to a Single Node Instance Over Public Networks,User Guide", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"dds_02_0080.html", + "product_code":"dds", + "code":"59", + "des":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.The default security group rule allows all ", + "doc_type":"usermanual", + "kw":"DDS DB instances,Setting a Security Group,Connecting to a Single Node Instance Over Public Networks,", + "title":"Setting a Security Group", + "githuburl":"" + }, + { + "uri":"dds_02_0048.html", + "product_code":"dds", + "code":"60", + "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 ", + "doc_type":"usermanual", + "kw":"DDS DB instance,Connecting to a Single Node Instance Over Public Networks,Connecting to a Single Nod", + "title":"Connecting to a Single Node Instance Over Public Networks", + "githuburl":"" + }, + { + "uri":"dds_03_0062.html", + "product_code":"dds", + "code":"61", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Permissions Management", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"dds_03_0060.html", + "product_code":"dds", + "code":"62", + "des":"This section describes how to use IAM to implement fine-grained permissions control for your DDS resources. With IAM, you can:Create IAM users for employees based on the ", + "doc_type":"usermanual", + "kw":"Creating a User and Granting Permissions,Permissions Management,User Guide", + "title":"Creating a User and Granting Permissions", + "githuburl":"" + }, + { + "uri":"dds_03_0061.html", + "product_code":"dds", + "code":"63", + "des":"Custom policies can be created as a supplement to the system policies of DDS. For the actions supported for custom policies, see DDS Actions.You can create custom policie", + "doc_type":"usermanual", + "kw":"Creating a Custom Policy,Permissions Management,User Guide", + "title":"Creating a Custom Policy", + "githuburl":"" + }, + { + "uri":"dds_03_0019.html", + "product_code":"dds", + "code":"64", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connection Management", + "title":"Connection Management", + "githuburl":"" + }, + { + "uri":"dds_03_0074.html", + "product_code":"dds", + "code":"65", + "des":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a DB instance using SSL. For details, see sec", + "doc_type":"usermanual", + "kw":"connect to a DB instance,connect to the DB instance,Enabling or Disabling SSL,Connection Management,", + "title":"Enabling or Disabling SSL", + "githuburl":"" + }, + { + "uri":"dds_03_0100.html", + "product_code":"dds", + "code":"66", + "des":"If a client and a replica set instance are deployed in different CIDR blocks and the client is not in 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8, configure Cross-CIDR A", + "doc_type":"usermanual", + "kw":"Configuring Cross-CIDR Access for Replica Set Instances,Connection Management,User Guide", + "title":"Configuring Cross-CIDR Access for Replica Set Instances", + "githuburl":"" + }, + { + "uri":"dds_02_0100.html", + "product_code":"dds", + "code":"67", + "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", + "doc_type":"usermanual", + "kw":"Enabling IP Addresses of shard and config Nodes,Connection Management,User Guide", + "title":"Enabling IP Addresses of shard and config Nodes", + "githuburl":"" + }, + { + "uri":"dds_03_0070.html", + "product_code":"dds", + "code":"68", + "des":"After a database is migrated from on-premises or other cloud platforms to DDS, the private IP address of the database may be changed. DDS allows you to change the private", + "doc_type":"usermanual", + "kw":"Changing a Private IP Address,Connection Management,User Guide", + "title":"Changing a Private IP Address", + "githuburl":"" + }, + { + "uri":"dds_03_change_database_port.html", + "product_code":"dds", + "code":"69", + "des":"This section guides you on how to modify the database port. The database port cannot be changed when the instance is in any of the following statuses:RestartingAdding nod", + "doc_type":"usermanual", + "kw":"Changing the Database Port,Connection Management,User Guide", + "title":"Changing the Database Port", + "githuburl":"" + }, + { + "uri":"dds_03_change_security_group.html", + "product_code":"dds", + "code":"70", + "des":"This section guides you on how to change a security group for cluster, replica set, and single node instances. If any of the following operations is in progress, do not c", + "doc_type":"usermanual", + "kw":"Changing a Security Group,Connection Management,User Guide", + "title":"Changing a Security Group", + "githuburl":"" + }, + { + "uri":"dds_03_0080.html", + "product_code":"dds", + "code":"71", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Commands", + "title":"Database Commands", + "githuburl":"" + }, + { + "uri":"dds_03_0033.html", + "product_code":"dds", + "code":"72", + "des":"The following tables list the commands supported and restricted by DDS.For more information, see official MongoDB documentation.Users cannot execute a system command.", + "doc_type":"usermanual", + "kw":"Which Commands are Supported or Restricted by DDS?,Database Commands,User Guide", + "title":"Which Commands are Supported or Restricted by DDS?", + "githuburl":"" + }, + { + "uri":"dds_03_0052.html", + "product_code":"dds", + "code":"73", + "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", + "doc_type":"usermanual", + "kw":"Migrating Data,User Guide", + "title":"Migrating Data", "githuburl":"" }, { "uri":"dds_03_0001.html", "product_code":"dds", - "code":"41", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Managing DDS DB Instances", - "title":"Managing DDS DB Instances", + "kw":"Account Management", + "title":"Account Management", + "githuburl":"" + }, + { + "uri":"dds_03_0057.html", + "product_code":"dds", + "code":"75", + "des":"This section describes how to create a database account and change the account password using commands after the DDS DB instances are created. When creating a database ac", + "doc_type":"usermanual", + "kw":"DDS DB instance,Creating a Database Account Using Commands,Account Management,User Guide", + "title":"Creating a Database Account Using Commands", + "githuburl":"" + }, + { + "uri":"dds_03_reset_password.html", + "product_code":"dds", + "code":"76", + "des":"For security reasons, you are advised to periodically change administrator passwords.You cannot reset the administrator password under the following circumstances:Restart", + "doc_type":"usermanual", + "kw":"Resetting the Administrator Password,Account Management,User Guide", + "title":"Resetting the Administrator Password", "githuburl":"" }, { "uri":"dds_03_0002.html", "product_code":"dds", - "code":"42", + "code":"77", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"DB Instance Operations", - "title":"DB Instance Operations", + "kw":"Instance Management", + "title":"Instance Management", "githuburl":"" }, { "uri":"dds_03_0075.html", "product_code":"dds", - "code":"43", - "des":"This section guides you on how to modify the DB instance name to identify different DB instances.If you want to submit the change, click OK. The DB instance name can be 4", + "code":"78", + "des":"This section describes how to change a DB instance name to identify different DB instances.If you want to submit the change, click OK. The DB instance name can be 4 to 64", "doc_type":"usermanual", - "kw":"Modifying the DB Instance Name,DB Instance Operations,User Guide", - "title":"Modifying the DB Instance Name", + "kw":"Changing a DB Instance Name,Instance Management,User Guide", + "title":"Changing a DB Instance Name", "githuburl":"" }, { - "uri":"dds_03_0051.html", + "uri":"en-us_topic_increase_nodes.html", "product_code":"dds", - "code":"44", - "des":"This section guides you on how to export DB instance information for analysis.", + "code":"79", + "des":"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 insta", "doc_type":"usermanual", - "kw":"Exporting DB Instance Information,DB Instance Operations,User Guide", - "title":"Exporting DB Instance Information", + "kw":"Adding Nodes to a Cluster,Instance Management,User Guide", + "title":"Adding Nodes to a Cluster", + "githuburl":"" + }, + { + "uri":"dds_03_0018.html", + "product_code":"dds", + "code":"80", + "des":"This section describes how to revert nodes that fail to be added.During reversal, the instance status is Deleting node. This process takes about 1 to 3 minutes.During del", + "doc_type":"usermanual", + "kw":"Reverting and Deleting Failed Cluster Instance Nodes,Instance Management,User Guide", + "title":"Reverting and Deleting Failed Cluster Instance Nodes", + "githuburl":"" + }, + { + "uri":"en-us_topic_increase_storage.html", + "product_code":"dds", + "code":"81", + "des":"This section describes how to scale up the storage space of a DB instance to suit your service requirements.You can scale up a DB instance a maximum of eight times.You ca", + "doc_type":"usermanual", + "kw":"Scaling Up Storage Space,Instance Management,User Guide", + "title":"Scaling Up Storage Space", + "githuburl":"" + }, + { + "uri":"en-us_topic_0000001159335385.html", + "product_code":"dds", + "code":"82", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Changing the DB Instance Class", + "title":"Changing the DB Instance Class", + "githuburl":"" + }, + { + "uri":"en-us_topic_0104472218.html", + "product_code":"dds", + "code":"83", + "des":"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", + "doc_type":"usermanual", + "kw":"Changing a Cluster DB Instance Class,Changing the DB Instance Class,User Guide", + "title":"Changing a Cluster DB Instance Class", + "githuburl":"" + }, + { + "uri":"en-us_topic_0104721795.html", + "product_code":"dds", + "code":"84", + "des":"Alternatively, on the Instance Management page, click the name of the replica set instance. In the DB Information area on the Basic Information page, click Change to the ", + "doc_type":"usermanual", + "kw":"Changing a Replica Set DB Instance Class,Changing the DB Instance Class,User Guide", + "title":"Changing a Replica Set DB Instance Class", + "githuburl":"" + }, + { + "uri":"dds_03_0030.html", + "product_code":"dds", + "code":"85", + "des":"Alternatively, on the Instance Management page, click the name of the single node instance. In the DB Information area on the Basic Information page, click Change to the ", + "doc_type":"usermanual", + "kw":"Changing a Single Node DB Instance Class,Changing the DB Instance Class,User Guide", + "title":"Changing a Single Node DB Instance Class", "githuburl":"" }, { "uri":"dds_03_0050.html", "product_code":"dds", - "code":"45", + "code":"86", "des":"A replica set consists of the primary node, secondary node, and hidden node. Primary and secondary nodes allow access from external services by providing IP addresses. Hi", "doc_type":"usermanual", - "kw":"Manually Switching the Primary and Secondary Nodes of a Replica Set,DB Instance Operations,User Guid", + "kw":"Manually Switching the Primary and Secondary Nodes of a Replica Set,Instance Management,User Guide", "title":"Manually Switching the Primary and Secondary Nodes of a Replica Set", "githuburl":"" }, + { + "uri":"dds_03_0051.html", + "product_code":"dds", + "code":"87", + "des":"This section describes how to export DB instance information for analysis. The following information can be exported:Database TypeDB Instance NameDB Instance IDDB Instanc", + "doc_type":"usermanual", + "kw":"Exporting DB Instance Information,Instance Management,User Guide", + "title":"Exporting DB Instance Information", + "githuburl":"" + }, { "uri":"dds_03_0003.html", "product_code":"dds", - "code":"46", - "des":"You may need to restart a DB instance for maintenance purposes. After modifying some parameters, you must restart the DB instance for the modifications to take effect on ", + "code":"88", + "des":"You may need to occasionally restart a DB instance to perform routine maintenance. For example, after modifying certain parameters, you must restart the DB instance for t", "doc_type":"usermanual", - "kw":"Restarting a DB Instance or a Node,DB Instance Operations,User Guide", + "kw":"Restarting a DB Instance or a Node,Instance Management,User Guide", "title":"Restarting a DB Instance or a Node", "githuburl":"" }, { "uri":"dds_03_0004.html", "product_code":"dds", - "code":"47", + "code":"89", "des":"This section guides you on how to delete a DB instance no longer used to release resources. You can delete the following types of DB instances:Cluster instanceReplica set", "doc_type":"usermanual", - "kw":"Deleting a DB instance,DB Instance Operations,User Guide", - "title":"Deleting a DB instance", + "kw":"Deleting a DB Instance,Instance Management,User Guide", + "title":"Deleting a DB Instance", "githuburl":"" }, { - "uri":"dds_03_0057.html", + "uri":"dds_03_0101.html", "product_code":"dds", - "code":"48", - "des":"This section guides you through how to create a database account and change the account password to manage the instances you created. When creating a database account for", + "code":"90", + "des":"DDS can move deleted DB instances to the recycle bin, so you can restore them easily.The recycling policy is enabled by default and cannot be disabled. Instances in the r", "doc_type":"usermanual", - "kw":"DDS DB instance,Managing Database Accounts,Managing DDS DB Instances,User Guide", - "title":"Managing Database Accounts", - "githuburl":"" - }, - { - "uri":"dds_03_0052.html", - "product_code":"dds", - "code":"49", - "des":"DDS supports access through EIPs by enabling public accessibility. You can also access a database through an ECS in the private network.Before migrating data from a Mongo", - "doc_type":"usermanual", - "kw":"MongoDB database,DDS DB instance,DB instance,Migrating Data,Managing DDS DB Instances,User Guide", - "title":"Migrating Data", + "kw":"Recycling a DB Instance,Instance Management,User Guide", + "title":"Recycling a DB Instance", "githuburl":"" }, { "uri":"dds_03_0006.html", "product_code":"dds", - "code":"50", + "code":"91", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup and Restore", @@ -502,7 +912,7 @@ { "uri":"en-us_topic_backup_restore.html", "product_code":"dds", - "code":"51", + "code":"92", "des":"DDS backs up data automatically based on the automated backup policy you set. You are advised to regularly back up data in your database. If the database becomes faulty o", "doc_type":"usermanual", "kw":"Setting Automated Backup Policy,Backup and Restore,User Guide", @@ -512,8 +922,8 @@ { "uri":"dds_03_0007.html", "product_code":"dds", - "code":"52", - "des":"This section guides you on how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.When ", + "code":"93", + "des":"This section describes how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.When you ", "doc_type":"usermanual", "kw":"Creating a Manual Backup,Backup and Restore,User Guide", "title":"Creating a Manual Backup", @@ -522,8 +932,8 @@ { "uri":"dds_03_0042.html", "product_code":"dds", - "code":"53", - "des":"This section guides you on how to restore a DB instance from a backup.Currently, DDS only supports restoring backups to a new DB instance.You are recommended to deploy th", + "code":"94", + "des":"This section describes how to restore a cluster instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and ", "doc_type":"usermanual", "kw":"Restoring a Cluster Instance from a Backup,Backup and Restore,User Guide", "title":"Restoring a Cluster Instance from a Backup", @@ -532,17 +942,37 @@ { "uri":"dds_03_0043.html", "product_code":"dds", - "code":"54", - "des":"This section guides you on how to restore a replica set instance from a backup.Currently, DDS only supports restoring backups to a new DB instance.You are recommended to ", + "code":"95", + "des":"This section describes how to restore a replica set instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS ", "doc_type":"usermanual", "kw":"Restoring a Replica Set Instance from a Backup,Backup and Restore,User Guide", "title":"Restoring a Replica Set Instance from a Backup", "githuburl":"" }, + { + "uri":"dds_03_0064.html", + "product_code":"dds", + "code":"96", + "des":"You can restore the data of a replica set instance to a specified time point.Currently, you can restore a replica set instance to a new or original DB instance at a point", + "doc_type":"usermanual", + "kw":"Restoring Replica Set Instance to a Point in Time,Backup and Restore,User Guide", + "title":"Restoring Replica Set Instance to a Point in Time", + "githuburl":"" + }, + { + "uri":"dds_03_0031.html", + "product_code":"dds", + "code":"97", + "des":"This section describes how to restore a single node instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS ", + "doc_type":"usermanual", + "kw":"Restoring a Single Node Instance from a Backup,Backup and Restore,User Guide", + "title":"Restoring a Single Node Instance from a Backup", + "githuburl":"" + }, { "uri":"en-us_topic_backup_download.html", "product_code":"dds", - "code":"55", + "code":"98", "des":"This section describes how to download manual or automated backup files for local data backup or restoration.For details on how to log in to OBS Browser, see section Logg", "doc_type":"usermanual", "kw":"Downloading Backup Files,Backup and Restore,User Guide", @@ -552,7 +982,7 @@ { "uri":"dds_03_0008.html", "product_code":"dds", - "code":"56", + "code":"99", "des":"This section describes how to delete manual backups to release the storage space.The deletion operation is irreversible. Exercise caution when performing this operation.B", "doc_type":"usermanual", "kw":"Deleting a Manual Backup,Backup and Restore,User Guide", @@ -562,8 +992,8 @@ { "uri":"dds_03_0009.html", "product_code":"dds", - "code":"57", - "des":"This section guides you on how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release sto", + "code":"100", + "des":"This section describes how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release storage", "doc_type":"usermanual", "kw":"Deleting an Automated Backup,Backup and Restore,User Guide", "title":"Deleting an Automated Backup", @@ -572,327 +1002,237 @@ { "uri":"dds_03_0010.html", "product_code":"dds", - "code":"58", + "code":"101", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Parameter Group", - "title":"Parameter Group", + "kw":"Parameter Template Management", + "title":"Parameter Template Management", "githuburl":"" }, { "uri":"en-us_topic_parameter_group.html", "product_code":"dds", - "code":"59", - "des":"DB parameter groups act as a container for engine configuration values that are applied to one or more DB instances. This section guides you on how to create a parameter ", + "code":"102", + "des":"DB parameter templates act as a container for engine configuration values that are applied to one or more DB instances.DDS does not share parameter template quotas with R", "doc_type":"usermanual", - "kw":"Creating a Parameter Group,Parameter Group,User Guide", - "title":"Creating a Parameter Group", + "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", + "title":"Creating a Parameter Template", "githuburl":"" }, { "uri":"en-us_topic_configuration.html", "product_code":"dds", - "code":"60", - "des":"This section guides you on how to edit parameters in the parameter groups that you have created to meet your service requirements and achieve optimal performance.Default ", + "code":"103", + "des":"You can modify parameters in custom parameter templates as needed to get the most out of DDS performance.You can modify parameters in either of the following ways:Directl", "doc_type":"usermanual", - "kw":"Editing a Parameter Group,Parameter Group,User Guide", - "title":"Editing a Parameter Group", + "kw":"Modifying a Parameter Template,Parameter Template Management,User Guide", + "title":"Modifying a Parameter Template", + "githuburl":"" + }, + { + "uri":"dds_03_0110.html", + "product_code":"dds", + "code":"104", + "des":"You can view the change history of a parameter template.In a newly exported or created parameter template, the change history is blank.You can apply the parameter templat", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", + "title":"Viewing Parameter Change History", + "githuburl":"" + }, + { + "uri":"dds_03_0111.html", + "product_code":"dds", + "code":"105", + "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to other instances by referring to Applying a Para", + "doc_type":"usermanual", + "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", + "title":"Exporting a Parameter Template", "githuburl":"" }, { "uri":"dds_03_0012.html", "product_code":"dds", - "code":"61", - "des":"This section guides you on how to compare two parameter groups of the same node type and DB engine version to know their current settings.If the settings of the two param", + "code":"106", + "des":"This section describes how to compare two parameter templates of the same node type and DB engine version.If their settings are different, the parameter names and values ", "doc_type":"usermanual", - "kw":"Comparing Two Parameter Groups,Parameter Group,User Guide", - "title":"Comparing Two Parameter Groups", + "kw":"Comparing Parameter Templates,Parameter Template Management,User Guide", + "title":"Comparing Parameter Templates", "githuburl":"" }, { "uri":"dds_03_0013.html", "product_code":"dds", - "code":"62", - "des":"This section guides you on how to replicate a parameter group you created and assign it a name different from that of original group.Parameter Group Name: specifies the p", + "code":"107", + "des":"You can replicate a parameter template you have created.Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones", "doc_type":"usermanual", - "kw":"Replicating a Parameter Group,Parameter Group,User Guide", - "title":"Replicating a Parameter Group", - "githuburl":"" - }, - { - "uri":"dds_03_0014.html", - "product_code":"dds", - "code":"63", - "des":"After a DB instance is created, you can change the parameter group associated with the DB instance to achieve optimal performance. The parameter group associated with the", - "doc_type":"usermanual", - "kw":"Changing Associated Parameter Group,Parameter Group,User Guide", - "title":"Changing Associated Parameter Group", + "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", + "title":"Replicating a Parameter Template", "githuburl":"" }, { "uri":"dds_03_0015.html", "product_code":"dds", - "code":"64", - "des":"This section guides you on how to reset all parameters in a parameter group you create to the default settings as needed.Resetting the parameter group will restore the de", + "code":"108", + "des":"This section describes how to reset all parameters in a parameter template you create to the default settings as needed.Resetting a parameter template will restore all pa", "doc_type":"usermanual", - "kw":"Resetting a Parameter Group,Parameter Group,User Guide", - "title":"Resetting a Parameter Group", + "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", + "title":"Resetting a Parameter Template", + "githuburl":"" + }, + { + "uri":"dds_03_0014.html", + "product_code":"dds", + "code":"109", + "des":"Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances or target node", + "doc_type":"usermanual", + "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", + "title":"Applying a Parameter Template", + "githuburl":"" + }, + { + "uri":"dds_03_0113.html", + "product_code":"dds", + "code":"110", + "des":"An application record contains information about performed apply operations. You can view the application records of a parameter template.Click Default Templates. Locate ", + "doc_type":"usermanual", + "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", + "title":"Viewing Application Records of a Parameter Template", "githuburl":"" }, { "uri":"dds_03_0044.html", "product_code":"dds", - "code":"65", - "des":"The section describes how to modify the description of the parameter group you created so that you can distinguish and identify parameter groups.", + "code":"111", + "des":"The section describes how to modify the description of a parameter template you created so that you can distinguish and identify parameter templates.", "doc_type":"usermanual", - "kw":"Changing a Parameter Group Description,Parameter Group,User Guide", - "title":"Changing a Parameter Group Description", + "kw":"Modifying the Description of a Parameter Template,Parameter Template Management,User Guide", + "title":"Modifying the Description of a Parameter Template", "githuburl":"" }, { "uri":"dds_03_0016.html", "product_code":"dds", - "code":"66", - "des":"This section guides you on how to delete a parameter group. The following parameter groups cannot be deleted.Default parameter groupsParameter groups associated with DB i", + "code":"112", + "des":"You can delete a custom parameter template that is no longer used.Default parameter templates and parameter templates applied to instances cannot be deleted.Deleted param", "doc_type":"usermanual", - "kw":"Deleting a Parameter Group,Parameter Group,User Guide", - "title":"Deleting a Parameter Group", - "githuburl":"" - }, - { - "uri":"dds_03_0017.html", - "product_code":"dds", - "code":"67", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Storage", - "title":"Storage", - "githuburl":"" - }, - { - "uri":"en-us_topic_increase_nodes.html", - "product_code":"dds", - "code":"68", - "des":"This section guides you on how to add nodes to a DB instance.You can add nodes when the instance status is Available, Deleting backup, or Checking restoration.A DB instan", - "doc_type":"usermanual", - "kw":"Adding Cluster Instance Nodes,Storage,User Guide", - "title":"Adding Cluster Instance Nodes", - "githuburl":"" - }, - { - "uri":"dds_03_0018.html", - "product_code":"dds", - "code":"69", - "des":"This section guides you on how to revert nodes that fail to be added.During reversal, the node status is Deleting node. This process takes about 1 to 3 minutes.During del", - "doc_type":"usermanual", - "kw":"Reverting Cluster Instance Nodes,Storage,User Guide", - "title":"Reverting Cluster Instance Nodes", - "githuburl":"" - }, - { - "uri":"en-us_topic_increase_storage.html", - "product_code":"dds", - "code":"70", - "des":"This section guides you on how to scale up the storage space of a DB instance to suit your service requirements.You can scale up a DB instance a maximum of eight times.Yo", - "doc_type":"usermanual", - "kw":"Scaling Up Storage Space,Storage,User Guide", - "title":"Scaling Up Storage Space", - "githuburl":"" - }, - { - "uri":"dds_08_0001.html", - "product_code":"dds", - "code":"71", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Changing DB Instance Classes", - "title":"Changing DB Instance Classes", - "githuburl":"" - }, - { - "uri":"en-us_topic_0104472218.html", - "product_code":"dds", - "code":"72", - "des":"This section guides you on how to change the CPU or memory of a cluster instance.A DB instance cannot be deleted when you are changing its CPU or memory.Instances can be ", - "doc_type":"usermanual", - "kw":"Changing the CPU or Memory of a Cluster DB Instance,Changing DB Instance Classes,User Guide", - "title":"Changing the CPU or Memory of a Cluster DB Instance", - "githuburl":"" - }, - { - "uri":"en-us_topic_0104721795.html", - "product_code":"dds", - "code":"73", - "des":"This section guides you on how to change the CPU or memory of your replica set instance.A DB instance cannot be deleted when you are changing its CPU or memory.Instances ", - "doc_type":"usermanual", - "kw":"Changing the CPU or Memory of a Replica Set DB Instance,Changing DB Instance Classes,User Guide", - "title":"Changing the CPU or Memory of a Replica Set DB Instance", - "githuburl":"" - }, - { - "uri":"dds_03_0019.html", - "product_code":"dds", - "code":"74", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Security", - "title":"Security", - "githuburl":"" - }, - { - "uri":"en-us_topic_reset_password.html", - "product_code":"dds", - "code":"75", - "des":"You are advised to change administrator passwords periodically to prevent password cracking, ensuring system security. You cannot reset the administrator password under t", - "doc_type":"usermanual", - "kw":"Resetting the Administrator Password,Security,User Guide", - "title":"Resetting the Administrator Password", - "githuburl":"" - }, - { - "uri":"en-us_topic_change_database_port.html", - "product_code":"dds", - "code":"76", - "des":"This section guides you on how to modify the database port to ensure system security. The database port cannot be changed when the instance is in any of the following sta", - "doc_type":"usermanual", - "kw":"Changing the Database Port,Security,User Guide", - "title":"Changing the Database Port", - "githuburl":"" - }, - { - "uri":"en-us_topic_change_security_group.html", - "product_code":"dds", - "code":"77", - "des":"This section guides you on how to change the security group of a DB instance. If any of the following operations is in progress, do not change the security group:Adding n", - "doc_type":"usermanual", - "kw":"Changing a Security Group,Security,User Guide", - "title":"Changing a Security Group", - "githuburl":"" - }, - { - "uri":"dds_03_0023.html", - "product_code":"dds", - "code":"78", - "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", - "doc_type":"usermanual", - "kw":"Tag,Managing DDS DB Instances,User Guide", - "title":"Tag", + "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", + "title":"Deleting a Parameter Template", "githuburl":"" }, { "uri":"dds_03_0040.html", "product_code":"dds", - "code":"79", - "des":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Currently, only the following tasks can be viewed:Creating a clus", + "code":"113", + "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", "doc_type":"usermanual", - "kw":"Task Center,Managing DDS DB Instances,User Guide", + "kw":"Task Center,User Guide", "title":"Task Center", "githuburl":"" }, - { - "uri":"dds_03_0024.html", - "product_code":"dds", - "code":"80", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Monitoring", - "title":"Monitoring", - "githuburl":"" - }, { "uri":"dds_03_0025.html", "product_code":"dds", - "code":"81", + "code":"114", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Interconnected with Cloud Eye", - "title":"Interconnected with Cloud Eye", + "kw":"Monitoring and Alarm Reporting", + "title":"Monitoring and Alarm Reporting", + "githuburl":"" + }, + { + "uri":"dds_03_0076.html", + "product_code":"dds", + "code":"115", + "des":"Cloud Eye monitors DDS instance metrics. You can obtain the monitoring metrics of DDS on the management console.Monitored data requires a period of time for transmission ", + "doc_type":"usermanual", + "kw":"DB instance,Viewing DDS Metrics,Monitoring and Alarm Reporting,User Guide", + "title":"Viewing DDS Metrics", "githuburl":"" }, { "uri":"dds_03_0026.html", "product_code":"dds", - "code":"82", - "des":"Table 1 lists the DB instance monitoring metrics.DB instance monitoring metricsMetricsUnitCOMMAND Statements per SecondCount/sDELETE Statements per SecondCount/sINSERT St", + "code":"116", + "des":"This section describes metrics reported by Document Database Service (DDS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye", "doc_type":"usermanual", - "kw":"DDS Metrics,Interconnected with Cloud Eye,User Guide", + "kw":"DDS Metrics,Monitoring and Alarm Reporting,User Guide", "title":"DDS Metrics", "githuburl":"" }, { "uri":"dds_03_0027.html", "product_code":"dds", - "code":"83", - "des":"You can set DDS alarm rules to customize the monitored objects and notification policies. Then, you can learn DDS running status in a timely manner.The DDS alarm rules in", + "code":"117", + "des":"You can enable the alarm reporting function in one click. After alarms are triggered, Simple Message Notification (SMN) can send notifications to specified cloud account.", "doc_type":"usermanual", - "kw":"Setting Alarm Rules,Interconnected with Cloud Eye,User Guide", + "kw":"Setting Alarm Rules,Monitoring and Alarm Reporting,User Guide", "title":"Setting Alarm Rules", "githuburl":"" }, - { - "uri":"dds_03_0078.html", - "product_code":"dds", - "code":"84", - "des":"Cloud Eye monitors DDS running statuses. You can obtain the monitoring metrics of DDS on the management console.Monitored data requires a period of time for transmission ", - "doc_type":"usermanual", - "kw":"DDS DB instance,DB instance,DDS DB instance,DB instance,DB instance,Viewing DDS Metrics,Interconnect", - "title":"Viewing DDS Metrics", - "githuburl":"" - }, { "uri":"dds_03_0028.html", "product_code":"dds", - "code":"85", + "code":"118", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Interconnecting with CTS", - "title":"Interconnecting with CTS", + "kw":"Auditing", + "title":"Auditing", "githuburl":"" }, { "uri":"dds_03_0029.html", "product_code":"dds", - "code":"86", - "des":"With CTS, you can record operations associated with DDS for later query, audit, and backtrack operations.", + "code":"119", + "des":"With Cloud Trace Service (CTS), you can record operations associated with DDS for later query, audit, and backtrack operations.ddsAddTag and ddsDeleteTag are respectively", "doc_type":"usermanual", - "kw":"Key Operations Recorded by CTS,Interconnecting with CTS,User Guide", + "kw":"Key Operations Recorded by CTS,Auditing,User Guide", "title":"Key Operations Recorded by CTS", "githuburl":"" }, { - "uri":"dds_03_0032.html", + "uri":"dds_03_0024.html", "product_code":"dds", - "code":"87", - "des":"After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.This section describ", + "code":"120", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Querying Traces,Interconnecting with CTS,User Guide", - "title":"Querying Traces", + "kw":"Log Management", + "title":"Log Management", "githuburl":"" }, { "uri":"en-us_topic_error_log.html", "product_code":"dds", - "code":"88", + "code":"121", "des":"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 proble", "doc_type":"usermanual", - "kw":"Error Log,Monitoring,User Guide", + "kw":"Error Log,Log Management,User Guide", "title":"Error Log", "githuburl":"" }, { "uri":"en-us_topic_slow_query_log.html", "product_code":"dds", - "code":"89", - "des":"Slow query logs record statements whose execution period exceeds the value of slowms (100 ms by default), allowing you identify and optimize slowly executed statements.Lo", + "code":"122", + "des":"Slow query logs record statements whose execution period exceeds the value of operationProfiling.slowOpThresholdMs (100 ms by default). With slow query logs, you can iden", "doc_type":"usermanual", - "kw":"Slow Query Log,Monitoring,User Guide", + "kw":"Slow Query Log,Log Management,User Guide", "title":"Slow Query Log", "githuburl":"" }, + { + "uri":"dds_03_0023.html", + "product_code":"dds", + "code":"123", + "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. Every cloud service is responsible for managing their own tags while T", + "doc_type":"usermanual", + "kw":"Tag Management,User Guide", + "title":"Tag Management", + "githuburl":"" + }, { "uri":"dds_faq_0100.html", "product_code":"dds", - "code":"90", + "code":"124", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -902,377 +1242,337 @@ { "uri":"dds_faq_0101.html", "product_code":"dds", - "code":"91", + "code":"125", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Common FAQs", - "title":"Common FAQs", + "kw":"Product Consulting", + "title":"Product Consulting", "githuburl":"" }, { "uri":"dds_faq_0001.html", "product_code":"dds", - "code":"92", - "des":"FailoverDDS uses multiple mongos, replica sets, and shards to ensure data reliability. When a mongos is faulty, the other mongos takes over services immediately to ensure", + "code":"126", + "des":"Precautions after applying for DDS:After purchasing DDS DB instances, you do not need to perform basic database O&M operations, such as HA and security patches. You need ", "doc_type":"usermanual", - "kw":"What Precautions Should Be Taken When Using DDS?,Common FAQs,User Guide", + "kw":"What Precautions Should Be Taken When Using DDS?,Product Consulting,User Guide", "title":"What Precautions Should Be Taken When Using DDS?", "githuburl":"" }, { "uri":"dds_faq_0002.html", "product_code":"dds", - "code":"93", + "code":"127", "des":"Formula for a DDS DB instance availability:DDS DB instance availability = (1 – Failure duration/Total service duration) × 100%.", "doc_type":"usermanual", - "kw":"What Is the Availability of DDS DB Instances?,Common FAQs,User Guide", + "kw":"What Is the Availability of DDS DB Instances?,Product Consulting,User Guide", "title":"What Is the Availability of DDS DB Instances?", "githuburl":"" }, - { - "uri":"dds_faq_0003.html", - "product_code":"dds", - "code":"94", - "des":"You do not need a template to create DDS DB instances. When you create a DB instance, DDS provides different DB instance specifications which are similar to templates.", - "doc_type":"usermanual", - "kw":"Can I Use a Template to Create DDS DB Instances?,Common FAQs,User Guide", - "title":"Can I Use a Template to Create DDS DB Instances?", - "githuburl":"" - }, { "uri":"dds_faq_0004.html", "product_code":"dds", - "code":"95", + "code":"128", "des":"No. Your DDS DB instances and resources are isolated from others.", "doc_type":"usermanual", - "kw":"Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?,Common FAQs,User Guide", + "kw":"Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?,Product Consulting,User Guide", "title":"Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?", "githuburl":"" }, { "uri":"dds_faq_0102.html", "product_code":"dds", - "code":"96", + "code":"129", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Management FAQs", - "title":"Management FAQs", + "kw":"Database Performance", + "title":"Database Performance", "githuburl":"" }, { "uri":"dds_faq_0005.html", "product_code":"dds", - "code":"97", + "code":"130", "des":"You can view the slow query logs to check whether any slowly executed SQL queries exist and view the performance characteristics of queries (if any) to locate the cause o", "doc_type":"usermanual", - "kw":"What Should I Do If My Query Is Slow?,Management FAQs,User Guide", + "kw":"What Should I Do If My Query Is Slow?,Database Performance,User Guide", "title":"What Should I Do If My Query Is Slow?", "githuburl":"" }, { "uri":"dds_faq_0006.html", "product_code":"dds", - "code":"98", + "code":"131", "des":"The delay for primary/secondary synchronization cannot be calculated using a formula. The delay is affected by the following factors:Network communication statusTransacti", "doc_type":"usermanual", - "kw":"What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?,Management FAQs,User ", + "kw":"What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?,Database Performance,", "title":"What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?", "githuburl":"" }, + { + "uri":"dds_faq_0103.html", + "product_code":"dds", + "code":"132", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Creation and Deletion", + "title":"Creation and Deletion", + "githuburl":"" + }, { "uri":"dds_faq_0007.html", "product_code":"dds", - "code":"99", + "code":"133", "des":"DDS does not delete or perform any operations on any user data. If this problem occurs, check whether a misoperation has been performed. Restore the data using backup fil", "doc_type":"usermanual", - "kw":"Why Is Data Missing from My Database?,Management FAQs,User Guide", + "kw":"Why Is Data Missing from My Database?,Creation and Deletion,User Guide", "title":"Why Is Data Missing from My Database?", "githuburl":"" }, { "uri":"dds_faq_0008.html", "product_code":"dds", - "code":"100", + "code":"134", "des":"If your cloud account is deleted, both your automated and manual backups are deleted.", "doc_type":"usermanual", - "kw":"Will My Backups Be Deleted If I Delete My Cloud Account?,Management FAQs,User Guide", + "kw":"Will My Backups Be Deleted If I Delete My Cloud Account?,Creation and Deletion,User Guide", "title":"Will My Backups Be Deleted If I Delete My Cloud Account?", "githuburl":"" }, - { - "uri":"dds_faq_0009.html", - "product_code":"dds", - "code":"101", - "des":"Yes. Adding shards does not affect the existing shards. Services are still available.", - "doc_type":"usermanual", - "kw":"Are My DDS DB Instances Available When Scaling?,Management FAQs,User Guide", - "title":"Are My DDS DB Instances Available When Scaling?", - "githuburl":"" - }, - { - "uri":"dds_faq_0010.html", - "product_code":"dds", - "code":"102", - "des":"Yes. DDS can perform write operations only on the primary node in a replica set. You can configure DDS to perform read operations on the secondary node to split read and ", - "doc_type":"usermanual", - "kw":"Does DDS Support Read/Write Splitting?,Management FAQs,User Guide", - "title":"Does DDS Support Read/Write Splitting?", - "githuburl":"" - }, { "uri":"dds_faq_0104.html", "product_code":"dds", - "code":"103", + "code":"135", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Connection and Access FAQs", - "title":"Connection and Access FAQs", - "githuburl":"" - }, - { - "uri":"dds_faq_0011.html", - "product_code":"dds", - "code":"104", - "des":"You can access the DDS DB instance using the following methods:Create a DDS DB instance and an ECS in the same VPC to enable the ECS to access the instance.If the DDS DB ", - "doc_type":"usermanual", - "kw":"Can an External Server Access the DDS DB Instance?,Connection and Access FAQs,User Guide", - "title":"Can an External Server Access the DDS DB Instance?", + "kw":"Database Connection", + "title":"Database Connection", "githuburl":"" }, { "uri":"dds_faq_0012.html", "product_code":"dds", - "code":"105", - "des":"The number of DDS database connections indicates the number of applications that can be simultaneously connected to the database. Generally, it indicates the number of co", + "code":"136", + "des":"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 maximu", "doc_type":"usermanual", - "kw":"connected to the database,What Is the Number of DDS Database Connections?,Connection and Access FAQs", + "kw":"What Is the Number of DDS Database Connections?,Database Connection,User Guide", "title":"What Is the Number of DDS Database Connections?", "githuburl":"" }, { "uri":"dds_faq_0013.html", "product_code":"dds", - "code":"106", - "des":"Perform the following steps to identify the problem: The following uses the cluster instance as an example.If they are in the same VPC, go to 2.If they are in different V", + "code":"137", + "des":"Perform the following steps to identify the problem:If yes, go to 3.If no, configure the VPC peering connection. For details, see \"VPC Peering Connection\" in Virtual Priv", "doc_type":"usermanual", - "kw":"What Should I Do If the ECS Cannot Connect to a DDS DB Instance?,Connection and Access FAQs,User Gui", - "title":"What Should I Do If the ECS Cannot Connect to a DDS DB Instance?", - "githuburl":"" - }, - { - "uri":"dds_faq_0014.html", - "product_code":"dds", - "code":"107", - "des":"Identify a DDS DB instance connection failure caused by a client problem from the following aspects.ECS Security PolicyIn Windows, check whether the DDS port is enabled i", - "doc_type":"usermanual", - "kw":"What Should I Do If a Database Client Problem Causes a Connection Failure?,Connection and Access FAQ", - "title":"What Should I Do If a Database Client Problem Causes a Connection Failure?", + "kw":"What Should I Do If an ECS Cannot Connect to a DDS DB Instance?,Database Connection,User Guide", + "title":"What Should I Do If an ECS Cannot Connect to a DDS DB Instance?", "githuburl":"" }, { "uri":"dds_faq_0015.html", "product_code":"dds", - "code":"108", + "code":"138", "des":"Check whether the following problems occur on the DDS database. Check the following one at a time.The maximum number of connections is reached.Solution: Use the Cloud Eye", "doc_type":"usermanual", - "kw":"What Should I Do If a DDS Server Problem Causes a Connection Failure?,Connection and Access FAQs,Use", + "kw":"What Should I Do If a DDS Server Problem Causes a Connection Failure?,Database Connection,User Guide", "title":"What Should I Do If a DDS Server Problem Causes a Connection Failure?", "githuburl":"" }, - { - "uri":"dds_faq_0016.html", - "product_code":"dds", - "code":"109", - "des":"Ensure that the ECS where in which your applications are located is in the same VPC and subnet as the DDS DB instance. If the ECS and the DDS DB instance are in different", - "doc_type":"usermanual", - "kw":"How Can My Applications Access a DDS DB Instance in a VPC?,Connection and Access FAQs,User Guide", - "title":"How Can My Applications Access a DDS DB Instance in a VPC?", - "githuburl":"" - }, - { - "uri":"dds_faq_0017.html", - "product_code":"dds", - "code":"110", - "des":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", - "doc_type":"usermanual", - "kw":"connect to the database,Do Applications Need to Support Automatic Reconnecting to the DDS Database?,", - "title":"Do Applications Need to Support Automatic Reconnecting to the DDS Database?", - "githuburl":"" - }, - { - "uri":"dds_faq_0034.html", - "product_code":"dds", - "code":"111", - "des":"For details on how to create and log in to an ECS, see \"Creating and Logging In to a Windows ECS\" or \"Creating and Logging In to a Linux ECS\" in the Elastic Cloud Server ", - "doc_type":"usermanual", - "kw":"How Can I Create and Log In to an ECS?,Connection and Access FAQs,User Guide", - "title":"How Can I Create and Log In to an ECS?", - "githuburl":"" - }, { "uri":"dds_faq_0018.html", "product_code":"dds", - "code":"112", + "code":"139", "des":"MongoDB official website provides client installation packages for different OSs. Download the official binary installation package at https://www.mongodb.com/download-ce", "doc_type":"usermanual", - "kw":"How Can I Install a MongoDB Client?,Connection and Access FAQs,User Guide", + "kw":"How Can I Install a MongoDB Client?,Database Connection,User Guide", "title":"How Can I Install a MongoDB Client?", "githuburl":"" }, { - "uri":"dds_faq_0108.html", + "uri":"dds_faq_0039.html", "product_code":"dds", - "code":"113", + "code":"140", + "des":"This section describes how to obtain the Robo 3T installation package and install Robo 3T.For details on how to connect to a cluster instance, see Connecting to a Cluster", + "doc_type":"usermanual", + "kw":"How Do I Install Robo 3T?,Database Connection,User Guide", + "title":"How Do I Install Robo 3T?", + "githuburl":"" + }, + { + "uri":"dds_faq_0105.html", + "product_code":"dds", + "code":"141", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Parameter and Metric FAQs", - "title":"Parameter and Metric FAQs", + "kw":"Database Usage", + "title":"Database Usage", "githuburl":"" }, { - "uri":"dds_faq_0019.html", + "uri":"dds_faq_0009.html", "product_code":"dds", - "code":"114", - "des":"You need to focus on the CPU, memory, and storage space usage.You can configure DDS to report alarms as needed. If an alarm is reported, you can take proper measures to c", + "code":"142", + "des":"Yes. Adding shards does not affect the existing shards. Services are still available.", "doc_type":"usermanual", - "kw":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?,Parameter and Metric FAQs,User Gu", - "title":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?", + "kw":"Are My DDS DB Instances Available When Scaling?,Database Usage,User Guide", + "title":"Are My DDS DB Instances Available When Scaling?", "githuburl":"" }, { - "uri":"dds_faq_0110.html", + "uri":"dds_faq_0107.html", "product_code":"dds", - "code":"115", + "code":"143", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Network and Security FAQs", - "title":"Network and Security FAQs", - "githuburl":"" - }, - { - "uri":"dds_faq_0021.html", - "product_code":"dds", - "code":"116", - "des":"DDS allows you to set the VPC which DDS DB instances belong to, ensuring that the DDS DB instances are isolated from other services. In addition, the IAM service is provi", - "doc_type":"usermanual", - "kw":"What Security Protection Policies Does DDS Have?,Network and Security FAQs,User Guide", - "title":"What Security Protection Policies Does DDS Have?", - "githuburl":"" - }, - { - "uri":"dds_faq_0022.html", - "product_code":"dds", - "code":"117", - "des":"A VPC allows you to create virtual network environment in a private and isolated network to control the private IP address range, subnets, route tables, and network gatew", - "doc_type":"usermanual", - "kw":"Do I Need to Use DDS in a VPC?,Network and Security FAQs,User Guide", - "title":"Do I Need to Use DDS in a VPC?", - "githuburl":"" - }, - { - "uri":"dds_faq_0023.html", - "product_code":"dds", - "code":"118", - "des":"The VPC security group helps ensure the security of DDS in a VPC. In addition, ACL can be used to allow or reject I/O network traffic for each subnet. Use the internal se", - "doc_type":"usermanual", - "kw":"How Do I Ensure the Security of DDS in a VPC?,Network and Security FAQs,User Guide", - "title":"How Do I Ensure the Security of DDS in a VPC?", - "githuburl":"" - }, - { - "uri":"dds_faq_0109.html", - "product_code":"dds", - "code":"119", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Storage FAQs", - "title":"Storage FAQs", - "githuburl":"" - }, - { - "uri":"dds_faq_0025.html", - "product_code":"dds", - "code":"120", - "des":"You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. You are advised to use the DDS backup function", - "doc_type":"usermanual", - "kw":"How Do I Back Up DDS to ECS?,Storage FAQs,User Guide", - "title":"How Do I Back Up DDS to ECS?", - "githuburl":"" - }, - { - "uri":"dds_faq_0026.html", - "product_code":"dds", - "code":"121", - "des":"The automated backup retention period is 7 days by default. You can set a backup retention period from 1 to 732 days. There is no limit on the manual backup retention per", - "doc_type":"usermanual", - "kw":"How Long Does DDS Store Backup Data For?,Storage FAQs,User Guide", - "title":"How Long Does DDS Store Backup Data For?", + "kw":"Database Storage", + "title":"Database Storage", "githuburl":"" }, { "uri":"dds_faq_0028.html", "product_code":"dds", - "code":"122", + "code":"144", "des":"The EVS is used for data storage of DDS DB instances. For details on the EVS, see Elastic Volume Service User Guide.The DDS DB instance backup data is stored in the OBS a", "doc_type":"usermanual", - "kw":"What Is the DDS DB Instance Storage Configuration?,Storage FAQs,User Guide", + "kw":"What Is the DDS DB Instance Storage Configuration?,Database Storage,User Guide", "title":"What Is the DDS DB Instance Storage Configuration?", "githuburl":"" }, { "uri":"dds_faq_0029.html", "product_code":"dds", - "code":"123", + "code":"145", "des":"If the storage space required by your applications exceeds the allowed maximum space allocated to you, you can do either of the following:Scale up storage space.Add shard", "doc_type":"usermanual", - "kw":"What Should I Do If My Data Exceeds the Database Storage Space of a DDS DB Instance?,Storage FAQs,Us", + "kw":"What Should I Do If My Data Exceeds the Database Storage Space of a DDS DB Instance?,Database Storag", "title":"What Should I Do If My Data Exceeds the Database Storage Space of a DDS DB Instance?", "githuburl":"" }, { "uri":"dds_faq_0030.html", "product_code":"dds", - "code":"124", - "des":"Both your common data (excluding backup data) and data required for ensuring DB instance proper running occupy the storage space on your purchased DDS DB instances. To en", + "code":"146", + "des":"The following types of data will occupy the storage space:User data except backupsData required for ensuring DB instance proper running occupy, such as system database da", "doc_type":"usermanual", - "kw":"Which Items Occupy the Storage Space on My Purchased DDS DB Instances?,Storage FAQs,User Guide", - "title":"Which Items Occupy the Storage Space on My Purchased DDS DB Instances?", + "kw":"Which Items Occupy the Storage Space of DDS DB Instances?,Database Storage,User Guide", + "title":"Which Items Occupy the Storage Space of DDS DB Instances?", "githuburl":"" }, { "uri":"dds_faq_0031.html", "product_code":"dds", - "code":"125", + "code":"147", "des":"The storage space you applied for will contain the system overhead required for inode, reserved block, and database operation.", "doc_type":"usermanual", - "kw":"What Overhead Does the Storage Space Have After I Applied for a DDS DB Instance?,Storage FAQs,User G", + "kw":"What Overhead Does the Storage Space Have After I Applied for a DDS DB Instance?,Database Storage,Us", "title":"What Overhead Does the Storage Space Have After I Applied for a DDS DB Instance?", "githuburl":"" }, + { + "uri":"dds_faq_0109.html", + "product_code":"dds", + "code":"148", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backup and Restoration", + "title":"Backup and Restoration", + "githuburl":"" + }, + { + "uri":"dds_faq_0025.html", + "product_code":"dds", + "code":"149", + "des":"You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. To ensure high data reliability and service as", + "doc_type":"usermanual", + "kw":"How Do I Back Up DDS Databases to an ECS?,Backup and Restoration,User Guide", + "title":"How Do I Back Up DDS Databases to an ECS?", + "githuburl":"" + }, + { + "uri":"dds_faq_0026.html", + "product_code":"dds", + "code":"150", + "des":"The automated backup retention period is 7 days by default. You can set a backup retention period from 1 to 732 days. There is no limit on the manual backup retention per", + "doc_type":"usermanual", + "kw":"How Long Does DDS Store Backup Data For?,Backup and Restoration,User Guide", + "title":"How Long Does DDS Store Backup Data For?", + "githuburl":"" + }, + { + "uri":"dds_faq_0110.html", + "product_code":"dds", + "code":"151", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Network Security", + "title":"Network Security", + "githuburl":"" + }, + { + "uri":"dds_faq_0021.html", + "product_code":"dds", + "code":"152", + "des":"DDS allows you to set the VPC which DDS DB instances belong to, ensuring that the DDS DB instances are isolated from other services. In addition, the IAM service is provi", + "doc_type":"usermanual", + "kw":"What Security Protection Policies Does DDS Have?,Network Security,User Guide", + "title":"What Security Protection Policies Does DDS Have?", + "githuburl":"" + }, + { + "uri":"dds_faq_0023.html", + "product_code":"dds", + "code":"153", + "des":"The VPC security group helps ensure the security of DDS in a VPC. In addition, ACL can be used to allow or reject I/O network traffic for each subnet. Use the internal se", + "doc_type":"usermanual", + "kw":"How Do I Ensure the Security of DDS in a VPC?,Network Security,User Guide", + "title":"How Do I Ensure the Security of DDS in a VPC?", + "githuburl":"" + }, + { + "uri":"dds_faq_0111.html", + "product_code":"dds", + "code":"154", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Resource Monitoring", + "title":"Resource Monitoring", + "githuburl":"" + }, + { + "uri":"dds_faq_0019.html", + "product_code":"dds", + "code":"155", + "des":"You need to focus on the CPU, memory, and storage space usage.You can configure DDS to report alarms as needed. If an alarm is reported, you can take proper measures to c", + "doc_type":"usermanual", + "kw":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?,Resource Monitoring,User Guide", + "title":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?", + "githuburl":"" + }, + { + "uri":"dds_faq_0112.html", + "product_code":"dds", + "code":"156", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, { "uri":"dds_faq_0032.html", "product_code":"dds", - "code":"126", + "code":"157", "des":"Logs and files listed in the following table occupy storage space.", "doc_type":"usermanual", - "kw":"Which Types of Logs and Files Occupy DDS DB Instance Storage Space?,Storage FAQs,User Guide", + "kw":"Which Types of Logs and Files Occupy DDS DB Instance Storage Space?,Log Management,User Guide", "title":"Which Types of Logs and Files Occupy DDS DB Instance Storage Space?", "githuburl":"" }, - { - "uri":"dds_faq_0033.html", - "product_code":"dds", - "code":"127", - "des":"The following tables list the commands supported and restricted by DDS.", - "doc_type":"usermanual", - "kw":"Which Commands are Supported or Restricted by DDS?,FAQs,User Guide", - "title":"Which Commands are Supported or Restricted by DDS?", - "githuburl":"" - }, { "uri":"dds_change_history.html", "product_code":"dds", - "code":"128", + "code":"158", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -1282,7 +1582,7 @@ { "uri":"dds_glossary.html", "product_code":"dds", - "code":"129", + "code":"159", "des":"For details about the glossaries in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", diff --git a/docs/dds/umn/CLASS.TXT.json b/docs/dds/umn/CLASS.TXT.json index 96a1b9421..14d38d33c 100644 --- a/docs/dds/umn/CLASS.TXT.json +++ b/docs/dds/umn/CLASS.TXT.json @@ -9,7 +9,7 @@ "code":"1" }, { - "desc":"Document Database Service (DDS) is compatible with MongoDB and is secure, highly available, reliable, scalable, and easy to use. It provides DB instance creation, scaling", + "desc":"Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB. It provides functions such", "product_code":"dds", "title":"What Is DDS?", "uri":"en-us_topic_introduction.html", @@ -27,23 +27,32 @@ "code":"3" }, { - "desc":"Each DDS cluster is an independent document database. A sharded cluster consists of mongos, config, and shard.Data read and write requests are forwarded by mongos. A mong", + "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", "product_code":"dds", - "title":"Cluster Architecture", + "title":"Cluster", "uri":"dds_01_0011.html", "doc_type":"usermanual", "p_code":"3", "code":"4" }, { - "desc":"A replica set consists of a set of mongod processes and provides a collection of data nodes to ensure data redundancy and reliability.For details about the mongod process", + "desc":"A replica set consists of a set of mongod processes. It is a collection of nodes that help ensure data redundancy and reliability.For details about the mongod process, se", "product_code":"dds", - "title":"Replica Set Architecture", + "title":"Replica Set", "uri":"dds_01_0012.html", "doc_type":"usermanual", "p_code":"3", "code":"5" }, + { + "desc":"A single node instance, as its name suggests, contains only one node which can be accessed directly.As a supplement to the cluster and replica set architectures, the sing", + "product_code":"dds", + "title":"Single Node Architecture", + "uri":"dds_01_0025.html", + "doc_type":"usermanual", + "p_code":"3", + "code":"6" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", @@ -51,25 +60,25 @@ "uri":"dds_01_0001.html", "doc_type":"usermanual", "p_code":"1", - "code":"6" + "code":"7" }, { - "desc":"DDS cluster instances consist of mongos, config, and shard nodes. The following diagram shows the node relationships.A mongos is a router for reading and writing data, pr", + "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", "product_code":"dds", "title":"Cluster", "uri":"dds_01_0002.html", "doc_type":"usermanual", - "p_code":"6", - "code":"7" + "p_code":"7", + "code":"8" }, { - "desc":"A database parameter group is a collection of configuration parameters and values and can be applied to multiple DB instances.", + "desc":"A database parameter template is a collection of configuration parameters and values and can be applied to multiple DB instances.", "product_code":"dds", - "title":"Database Parameter Group", + "title":"Database Parameter Template", "uri":"dds_01_0005.html", "doc_type":"usermanual", - "p_code":"6", - "code":"8" + "p_code":"7", + "code":"9" }, { "desc":"A region is a geographic area in which resources used by DDS are located.Each region comprises one or more AZs and is completely isolated from other regions. AZs within t", @@ -77,54 +86,27 @@ "title":"Regions and AZs", "uri":"dds_01_0027.html", "doc_type":"usermanual", - "p_code":"6", - "code":"9" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Product Advantages", - "uri":"dds_01_0006.html", - "doc_type":"usermanual", - "p_code":"1", + "p_code":"7", "code":"10" }, { - "desc":"The three-node replica set architecture of DDS ensures high service availability.In a replica set, both the primary and secondary nodes provide services. If a primary nod", + "desc":"DDS supports three deployment architectures: cluster, replica set, and single node. They meet requirements of different service scenarios.ClusterA cluster consists of thr", "product_code":"dds", - "title":"High Reliability", - "uri":"dds_01_0007.html", + "title":"Functions and Features", + "uri":"dds_01_0006.html", "doc_type":"usermanual", - "p_code":"10", + "p_code":"1", "code":"11" }, { - "desc":"DDS uses Virtual Private Clouds (VPCs) and network security groups to isolate your DB instances. VPCs allow you to configure IP address ranges that are allowed access to ", + "desc":"Game players' information generated from game applications, such as players' equipment and bonus points, are stored in DDS databases. During peak hours, DDS cluster insta", "product_code":"dds", - "title":"High Security", - "uri":"dds_01_0008.html", + "title":"Typical Application Scenarios", + "uri":"dds_01_0015.html", "doc_type":"usermanual", - "p_code":"10", + "p_code":"1", "code":"12" }, - { - "desc":"You can create a DB instance on the management console and access DDS through an Elastic Cloud Server (ECS) to reduce the application response time. If you need to access", - "product_code":"dds", - "title":"Ease of Use", - "uri":"dds_01_0010.html", - "doc_type":"usermanual", - "p_code":"10", - "code":"13" - }, - { - "desc":"DDS supports the cluster mode. You can select multiple mongos and shards. When your service changes or the current instance configuration cannot meet the application perf", - "product_code":"dds", - "title":"Scalability", - "uri":"dds_01_0009.html", - "doc_type":"usermanual", - "p_code":"10", - "code":"14" - }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", @@ -132,46 +114,64 @@ "uri":"dds_01_0013.html", "doc_type":"usermanual", "p_code":"1", - "code":"15" + "code":"13" }, { - "desc":"DB instance specifications are listed in the following table.DB instance specifications vary depending on the actual environment.For details about the cluster instance sp", + "desc":"DB instance specifications are listed in the following table.The DB instance specifications depend on service requirements.You can change the maximum number of connection", "product_code":"dds", "title":"DB Instance Specifications", "uri":"dds_01_0024.html", "doc_type":"usermanual", - "p_code":"15", - "code":"16" + "p_code":"13", + "code":"14" }, { - "desc":"Currently, DDS is compatible with MongoDB 3.2 and 3.4 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.", + "desc":"DDS is compatible with MongoDB 3.2, 3.4, 4.0, and 4.2 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.", "product_code":"dds", "title":"Database Engine and Version", "uri":"dds_01_0014.html", "doc_type":"usermanual", - "p_code":"15", - "code":"17" + "p_code":"13", + "code":"15" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Database Status", + "title":"DB Instance Status", "uri":"dds_01_0026.html", "doc_type":"usermanual", - "p_code":"15", + "p_code":"13", + "code":"16" + }, + { + "desc":"To improve the stability and security of DB instances, there are some constraints on the use of DDS. For details, see Table 1.", + "product_code":"dds", + "title":"Constraints and Recommendations", + "uri":"dds_01_0022.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"17" + }, + { + "desc":"IAM provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and user gr", + "product_code":"dds", + "title":"User Permissions", + "uri":"dds_01_0017.html", + "doc_type":"usermanual", + "p_code":"1", "code":"18" }, { - "desc":"Mobile Apps and MapsDDS supports two-dimensional space indexes for mobile applications (Apps) and maps that have location query requests. In addition, the dynamic storage", + "desc":"If you need to assign different permissions to employees in your enterprise to access your DDS resources, IAM is a good choice for fine-grained permissions management. IA", "product_code":"dds", - "title":"Typical Application Scenarios", - "uri":"dds_01_0015.html", + "title":"Permissions Management", + "uri":"dds_01_0019.html", "doc_type":"usermanual", "p_code":"1", "code":"19" }, { - "desc":"ECS provides DDS with elastic computing resources. DDS needs to apply for resources from ECS to build a running environment for DB instances.For more information, see the", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", "title":"Related Services", "uri":"dds_01_0016.html", @@ -180,22 +180,13 @@ "code":"20" }, { - "desc":"DDS provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user groups, and user gr", + "desc":"You have registered an account.For the first time you use DDS, apply for an account at the official website. After the application is successful, your account has permiss", "product_code":"dds", - "title":"User Permissions", - "uri":"dds_01_0017.html", - "doc_type":"usermanual", - "p_code":"1", - "code":"21" - }, - { - "desc":"You have registered an account.For the first time you use DDS, register an account at the official website. After the registration, your account has permissions to access", - "product_code":"dds", - "title":"Logging In to the DDS Console", + "title":"Logging in to the DDS Console", "uri":"dds_02_0043.html", "doc_type":"usermanual", "p_code":"", - "code":"22" + "code":"21" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -204,80 +195,116 @@ "uri":"dds_02_cluster.html", "doc_type":"usermanual", "p_code":"", + "code":"22" + }, + { + "desc":"You can access DDS over private or public networks.", + "product_code":"dds", + "title":"Connection Methods", + "uri":"dds_02_0001.html", + "doc_type":"usermanual", + "p_code":"22", "code":"23" }, - { - "desc":"This section describes how to create a cluster instance, set a security group, and connect to a cluster instance.Users who create the DDS DB instance for the first time.U", - "product_code":"dds", - "title":"Service Process", - "uri":"dds_02_0003.html", - "doc_type":"usermanual", - "p_code":"23", - "code":"24" - }, - { - "desc":"To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.", - "product_code":"dds", - "title":"Restrictions", - "uri":"dds_02_0002.html", - "doc_type":"usermanual", - "p_code":"23", - "code":"25" - }, - { - "desc":"This section describes how to create a DDS cluster instance of Community Edition on the DDS management console. DDS allows you to tailor your computing resources and stor", - "product_code":"dds", - "title":"Creating a Cluster Instance", - "uri":"dds_02_0008.html", - "doc_type":"usermanual", - "p_code":"23", - "code":"26" - }, - { - "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.You can access a DDS DB instance in either ", - "product_code":"dds", - "title":"Setting a Security Group", - "uri":"dds_02_0005.html", - "doc_type":"usermanual", - "p_code":"23", - "code":"27" - }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Connecting to a Cluster Instance", + "title":"Connecting to a Cluster Instance Over Private Networks", "uri":"dds_02_0009.html", "doc_type":"usermanual", - "p_code":"23", + "p_code":"22", + "code":"24" + }, + { + "desc":"This section describes how to create a cluster instance on the management console, set a security group, and connect to a cluster instance over private networks.The follo", + "product_code":"dds", + "title":"Overview", + "uri":"dds_02_0010.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"25" + }, + { + "desc":"This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space", + "product_code":"dds", + "title":"Creating a Cluster Instance", + "uri":"en-us_topic_0044018333.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"26" + }, + { + "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", + "product_code":"dds", + "title":"Setting a Security Group", + "uri":"dds_02_0022.html", + "doc_type":"usermanual", + "p_code":"24", + "code":"27" + }, + { + "desc":"This section describes how to connect to a cluster instance using the MongoDB client over private networks.The MongoDB client can connect to a DB instance with an unencry", + "product_code":"dds", + "title":"Connecting to a Cluster Instance Over Private Networks", + "uri":"en-us_topic_0044018334.html", + "doc_type":"usermanual", + "p_code":"24", "code":"28" }, { - "desc":"You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:Use a private IP address when:DDS provides a p", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Binding and Unbinding an EIP", - "uri":"dds_02_0006.html", + "title":"Connecting to a Cluster Instance Over Public Networks", + "uri":"dds_02_0013.html", "doc_type":"usermanual", - "p_code":"28", + "p_code":"22", "code":"29" }, { - "desc":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a database using SSL. For details, see SSL Co", + "desc":"This section describes how to create a cluster instance on the management console, set a security group, bind an EIP, and connect to a cluster instance over public networ", "product_code":"dds", - "title":"Enabling or Disabling SSL", - "uri":"dds_02_0007.html", + "title":"Overview", + "uri":"dds_02_0014.html", "doc_type":"usermanual", - "p_code":"28", + "p_code":"29", "code":"30" }, { - "desc":"This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt ", + "desc":"This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space", "product_code":"dds", - "title":"Connecting to a DB Instance Through a Client", - "uri":"en-us_topic_0044018334.html", + "title":"Creating a Cluster Instance", + "uri":"dds_02_0016.html", "doc_type":"usermanual", - "p_code":"28", + "p_code":"29", "code":"31" }, + { + "desc":"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", + "product_code":"dds", + "title":"Binding an EIP", + "uri":"dds_02_0046.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"32" + }, + { + "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", + "product_code":"dds", + "title":"Setting a Security Group", + "uri":"dds_02_0019.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"33" + }, + { + "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", + "product_code":"dds", + "title":"Connecting to a Cluster Instance Over Public Networks", + "uri":"dds_02_0006.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"34" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", @@ -285,160 +312,502 @@ "uri":"dds_02_replica_set.html", "doc_type":"usermanual", "p_code":"", - "code":"32" - }, - { - "desc":"This section describes how to create a replica set instance, set a security group, and connect to a replica set instance.Users who create the DDS DB instance for the firs", - "product_code":"dds", - "title":"Service Process", - "uri":"dds_02_0010.html", - "doc_type":"usermanual", - "p_code":"32", - "code":"33" - }, - { - "desc":"To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.", - "product_code":"dds", - "title":"Restrictions", - "uri":"dds_02_0011.html", - "doc_type":"usermanual", - "p_code":"32", - "code":"34" - }, - { - "desc":"This section describes how to create a DDS replica set instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your", - "product_code":"dds", - "title":"Creating a Replica Set Instance", - "uri":"dds_02_0012.html", - "doc_type":"usermanual", - "p_code":"32", "code":"35" }, { - "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group. This document describes how to set securit", + "desc":"You can access DDS over private or public networks.", "product_code":"dds", - "title":"Setting a Security Group", - "uri":"dds_02_0013.html", + "title":"Connection Methods", + "uri":"dds_02_0042.html", "doc_type":"usermanual", - "p_code":"32", + "p_code":"35", "code":"36" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Connecting to a Replica Set Instance", - "uri":"dds_02_0014.html", + "title":"Connecting to a Replica Set Instance Over Private Networks", + "uri":"dds_02_0055.html", "doc_type":"usermanual", - "p_code":"32", + "p_code":"35", "code":"37" }, { - "desc":"You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:Use a private IP address when:DDS provides a p", + "desc":"This section describes how to create a replica set instance on the management console, set a security group, and connect to a replica set instance over private networks.T", "product_code":"dds", - "title":"Binding and Unbinding an EIP", - "uri":"dds_02_0015.html", + "title":"Overview", + "uri":"dds_02_0057.html", "doc_type":"usermanual", "p_code":"37", "code":"38" }, { - "desc":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a database using SSL. For details, see SSL Co", + "desc":"This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your busin", "product_code":"dds", - "title":"Enabling or Disabling SSL", - "uri":"dds_02_0016.html", + "title":"Creating a Replica Set Instance", + "uri":"dds_02_0012.html", "doc_type":"usermanual", "p_code":"37", "code":"39" }, { - "desc":"This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt ", + "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how t", "product_code":"dds", - "title":"Connecting to a DB Instance Through a Client", - "uri":"en-us_topic_0105284966.html", + "title":"Setting a Security Group", + "uri":"dds_02_0049.html", "doc_type":"usermanual", "p_code":"37", "code":"40" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "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", "product_code":"dds", - "title":"Managing DDS DB Instances", - "uri":"dds_03_0001.html", + "title":"Connecting to a Replica Set Instance Over Private Networks", + "uri":"en-us_topic_0105284966.html", "doc_type":"usermanual", - "p_code":"", + "p_code":"37", "code":"41" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"DB Instance Operations", - "uri":"dds_03_0002.html", + "title":"Connecting to a Replica Set Instance Over Public Networks", + "uri":"dds_02_0050.html", "doc_type":"usermanual", - "p_code":"41", + "p_code":"35", "code":"42" }, { - "desc":"This section guides you on how to modify the DB instance name to identify different DB instances.If you want to submit the change, click OK. The DB instance name can be 4", + "desc":"This section describes how to create a replica set instance on the management console, set a security group, bind an EIP, and connect to a replica set instance over publi", "product_code":"dds", - "title":"Modifying the DB Instance Name", - "uri":"dds_03_0075.html", + "title":"Overview", + "uri":"dds_02_0051.html", "doc_type":"usermanual", "p_code":"42", "code":"43" }, { - "desc":"This section guides you on how to export DB instance information for analysis.", + "desc":"This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your busin", "product_code":"dds", - "title":"Exporting DB Instance Information", - "uri":"dds_03_0051.html", + "title":"Creating a Replica Set Instance", + "uri":"dds_02_0052.html", "doc_type":"usermanual", "p_code":"42", "code":"44" }, + { + "desc":"After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB", + "product_code":"dds", + "title":"Binding an EIP", + "uri":"dds_02_0053.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"45" + }, + { + "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how t", + "product_code":"dds", + "title":"Setting a Security Group", + "uri":"dds_02_0054.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"46" + }, + { + "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", + "product_code":"dds", + "title":"Connecting to a Replica Set Instance Over Public Networks", + "uri":"dds_02_0047.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"47" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Getting Started with Single Nodes", + "uri":"dds_02_single_node.html", + "doc_type":"usermanual", + "p_code":"", + "code":"48" + }, + { + "desc":"You can access DDS over private or public networks.", + "product_code":"dds", + "title":"Connection Methods", + "uri":"dds_02_0070.html", + "doc_type":"usermanual", + "p_code":"48", + "code":"49" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Connecting to a Single-Node Instance Over Private Networks", + "uri":"dds_02_0074.html", + "doc_type":"usermanual", + "p_code":"48", + "code":"50" + }, + { + "desc":"This section describes how to create a single node instance on the management console, set a security group, and connect to a single node instance over private networks.T", + "product_code":"dds", + "title":"Overview", + "uri":"dds_02_0075.html", + "doc_type":"usermanual", + "p_code":"50", + "code":"51" + }, + { + "desc":"This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your bus", + "product_code":"dds", + "title":"Creating a Single Node Instance", + "uri":"dds_02_0023.html", + "doc_type":"usermanual", + "p_code":"50", + "code":"52" + }, + { + "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.The default security group rule allows all ", + "product_code":"dds", + "title":"Setting a Security Group", + "uri":"dds_02_0024.html", + "doc_type":"usermanual", + "p_code":"50", + "code":"53" + }, + { + "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", + "product_code":"dds", + "title":"Connecting to a Single Node Instance Over Private Networks", + "uri":"dds_02_0028.html", + "doc_type":"usermanual", + "p_code":"50", + "code":"54" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Connecting to a Single Node Instance Over Public Networks", + "uri":"dds_02_0077.html", + "doc_type":"usermanual", + "p_code":"48", + "code":"55" + }, + { + "desc":"This section describes how to create a single node instance on the management console, set a security group, bind an EIP, and connect to a single node instance over publi", + "product_code":"dds", + "title":"Overview", + "uri":"dds_02_0078.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"56" + }, + { + "desc":"This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your bus", + "product_code":"dds", + "title":"Creating a Single Node Instance", + "uri":"dds_02_0079.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"57" + }, + { + "desc":"After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB", + "product_code":"dds", + "title":"Binding an EIP", + "uri":"dds_02_0026.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"58" + }, + { + "desc":"This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.The default security group rule allows all ", + "product_code":"dds", + "title":"Setting a Security Group", + "uri":"dds_02_0080.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"59" + }, + { + "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 ", + "product_code":"dds", + "title":"Connecting to a Single Node Instance Over Public Networks", + "uri":"dds_02_0048.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"60" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Permissions Management", + "uri":"dds_03_0062.html", + "doc_type":"usermanual", + "p_code":"", + "code":"61" + }, + { + "desc":"This section describes how to use IAM to implement fine-grained permissions control for your DDS resources. With IAM, you can:Create IAM users for employees based on the ", + "product_code":"dds", + "title":"Creating a User and Granting Permissions", + "uri":"dds_03_0060.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"62" + }, + { + "desc":"Custom policies can be created as a supplement to the system policies of DDS. For the actions supported for custom policies, see DDS Actions.You can create custom policie", + "product_code":"dds", + "title":"Creating a Custom Policy", + "uri":"dds_03_0061.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"63" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Connection Management", + "uri":"dds_03_0019.html", + "doc_type":"usermanual", + "p_code":"", + "code":"64" + }, + { + "desc":"DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.If SSL is enabled, you can connect to a DB instance using SSL. For details, see sec", + "product_code":"dds", + "title":"Enabling or Disabling SSL", + "uri":"dds_03_0074.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"65" + }, + { + "desc":"If a client and a replica set instance are deployed in different CIDR blocks and the client is not in 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8, configure Cross-CIDR A", + "product_code":"dds", + "title":"Configuring Cross-CIDR Access for Replica Set Instances", + "uri":"dds_03_0100.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"66" + }, + { + "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", + "product_code":"dds", + "title":"Enabling IP Addresses of shard and config Nodes", + "uri":"dds_02_0100.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"67" + }, + { + "desc":"After a database is migrated from on-premises or other cloud platforms to DDS, the private IP address of the database may be changed. DDS allows you to change the private", + "product_code":"dds", + "title":"Changing a Private IP Address", + "uri":"dds_03_0070.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"68" + }, + { + "desc":"This section guides you on how to modify the database port. The database port cannot be changed when the instance is in any of the following statuses:RestartingAdding nod", + "product_code":"dds", + "title":"Changing the Database Port", + "uri":"dds_03_change_database_port.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"69" + }, + { + "desc":"This section guides you on how to change a security group for cluster, replica set, and single node instances. If any of the following operations is in progress, do not c", + "product_code":"dds", + "title":"Changing a Security Group", + "uri":"dds_03_change_security_group.html", + "doc_type":"usermanual", + "p_code":"64", + "code":"70" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Database Commands", + "uri":"dds_03_0080.html", + "doc_type":"usermanual", + "p_code":"", + "code":"71" + }, + { + "desc":"The following tables list the commands supported and restricted by DDS.For more information, see official MongoDB documentation.Users cannot execute a system command.", + "product_code":"dds", + "title":"Which Commands are Supported or Restricted by DDS?", + "uri":"dds_03_0033.html", + "doc_type":"usermanual", + "p_code":"71", + "code":"72" + }, + { + "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", + "product_code":"dds", + "title":"Migrating Data", + "uri":"dds_03_0052.html", + "doc_type":"usermanual", + "p_code":"", + "code":"73" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Account Management", + "uri":"dds_03_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"74" + }, + { + "desc":"This section describes how to create a database account and change the account password using commands after the DDS DB instances are created. When creating a database ac", + "product_code":"dds", + "title":"Creating a Database Account Using Commands", + "uri":"dds_03_0057.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"75" + }, + { + "desc":"For security reasons, you are advised to periodically change administrator passwords.You cannot reset the administrator password under the following circumstances:Restart", + "product_code":"dds", + "title":"Resetting the Administrator Password", + "uri":"dds_03_reset_password.html", + "doc_type":"usermanual", + "p_code":"74", + "code":"76" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Instance Management", + "uri":"dds_03_0002.html", + "doc_type":"usermanual", + "p_code":"", + "code":"77" + }, + { + "desc":"This section describes how to change a DB instance name to identify different DB instances.If you want to submit the change, click OK. The DB instance name can be 4 to 64", + "product_code":"dds", + "title":"Changing a DB Instance Name", + "uri":"dds_03_0075.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"78" + }, + { + "desc":"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 insta", + "product_code":"dds", + "title":"Adding Nodes to a Cluster", + "uri":"en-us_topic_increase_nodes.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"79" + }, + { + "desc":"This section describes how to revert nodes that fail to be added.During reversal, the instance status is Deleting node. This process takes about 1 to 3 minutes.During del", + "product_code":"dds", + "title":"Reverting and Deleting Failed Cluster Instance Nodes", + "uri":"dds_03_0018.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"80" + }, + { + "desc":"This section describes how to scale up the storage space of a DB instance to suit your service requirements.You can scale up a DB instance a maximum of eight times.You ca", + "product_code":"dds", + "title":"Scaling Up Storage Space", + "uri":"en-us_topic_increase_storage.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"81" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Changing the DB Instance Class", + "uri":"en-us_topic_0000001159335385.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"82" + }, + { + "desc":"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", + "product_code":"dds", + "title":"Changing a Cluster DB Instance Class", + "uri":"en-us_topic_0104472218.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"83" + }, + { + "desc":"Alternatively, on the Instance Management page, click the name of the replica set instance. In the DB Information area on the Basic Information page, click Change to the ", + "product_code":"dds", + "title":"Changing a Replica Set DB Instance Class", + "uri":"en-us_topic_0104721795.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"84" + }, + { + "desc":"Alternatively, on the Instance Management page, click the name of the single node instance. In the DB Information area on the Basic Information page, click Change to the ", + "product_code":"dds", + "title":"Changing a Single Node DB Instance Class", + "uri":"dds_03_0030.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"85" + }, { "desc":"A replica set consists of the primary node, secondary node, and hidden node. Primary and secondary nodes allow access from external services by providing IP addresses. Hi", "product_code":"dds", "title":"Manually Switching the Primary and Secondary Nodes of a Replica Set", "uri":"dds_03_0050.html", "doc_type":"usermanual", - "p_code":"42", - "code":"45" + "p_code":"77", + "code":"86" }, { - "desc":"You may need to restart a DB instance for maintenance purposes. After modifying some parameters, you must restart the DB instance for the modifications to take effect on ", + "desc":"This section describes how to export DB instance information for analysis. The following information can be exported:Database TypeDB Instance NameDB Instance IDDB Instanc", + "product_code":"dds", + "title":"Exporting DB Instance Information", + "uri":"dds_03_0051.html", + "doc_type":"usermanual", + "p_code":"77", + "code":"87" + }, + { + "desc":"You may need to occasionally restart a DB instance to perform routine maintenance. For example, after modifying certain parameters, you must restart the DB instance for t", "product_code":"dds", "title":"Restarting a DB Instance or a Node", "uri":"dds_03_0003.html", "doc_type":"usermanual", - "p_code":"42", - "code":"46" + "p_code":"77", + "code":"88" }, { "desc":"This section guides you on how to delete a DB instance no longer used to release resources. You can delete the following types of DB instances:Cluster instanceReplica set", "product_code":"dds", - "title":"Deleting a DB instance", + "title":"Deleting a DB Instance", "uri":"dds_03_0004.html", "doc_type":"usermanual", - "p_code":"42", - "code":"47" + "p_code":"77", + "code":"89" }, { - "desc":"This section guides you through how to create a database account and change the account password to manage the instances you created. When creating a database account for", + "desc":"DDS can move deleted DB instances to the recycle bin, so you can restore them easily.The recycling policy is enabled by default and cannot be disabled. Instances in the r", "product_code":"dds", - "title":"Managing Database Accounts", - "uri":"dds_03_0057.html", + "title":"Recycling a DB Instance", + "uri":"dds_03_0101.html", "doc_type":"usermanual", - "p_code":"41", - "code":"48" - }, - { - "desc":"DDS supports access through EIPs by enabling public accessibility. You can also access a database through an ECS in the private network.Before migrating data from a Mongo", - "product_code":"dds", - "title":"Migrating Data", - "uri":"dds_03_0052.html", - "doc_type":"usermanual", - "p_code":"41", - "code":"49" + "p_code":"77", + "code":"90" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -446,8 +815,8 @@ "title":"Backup and Restore", "uri":"dds_03_0006.html", "doc_type":"usermanual", - "p_code":"41", - "code":"50" + "p_code":"", + "code":"91" }, { "desc":"DDS backs up data automatically based on the automated backup policy you set. You are advised to regularly back up data in your database. If the database becomes faulty o", @@ -455,35 +824,53 @@ "title":"Setting Automated Backup Policy", "uri":"en-us_topic_backup_restore.html", "doc_type":"usermanual", - "p_code":"50", - "code":"51" + "p_code":"91", + "code":"92" }, { - "desc":"This section guides you on how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.When ", + "desc":"This section describes how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.When you ", "product_code":"dds", "title":"Creating a Manual Backup", "uri":"dds_03_0007.html", "doc_type":"usermanual", - "p_code":"50", - "code":"52" + "p_code":"91", + "code":"93" }, { - "desc":"This section guides you on how to restore a DB instance from a backup.Currently, DDS only supports restoring backups to a new DB instance.You are recommended to deploy th", + "desc":"This section describes how to restore a cluster instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and ", "product_code":"dds", "title":"Restoring a Cluster Instance from a Backup", "uri":"dds_03_0042.html", "doc_type":"usermanual", - "p_code":"50", - "code":"53" + "p_code":"91", + "code":"94" }, { - "desc":"This section guides you on how to restore a replica set instance from a backup.Currently, DDS only supports restoring backups to a new DB instance.You are recommended to ", + "desc":"This section describes how to restore a replica set instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS ", "product_code":"dds", "title":"Restoring a Replica Set Instance from a Backup", "uri":"dds_03_0043.html", "doc_type":"usermanual", - "p_code":"50", - "code":"54" + "p_code":"91", + "code":"95" + }, + { + "desc":"You can restore the data of a replica set instance to a specified time point.Currently, you can restore a replica set instance to a new or original DB instance at a point", + "product_code":"dds", + "title":"Restoring Replica Set Instance to a Point in Time", + "uri":"dds_03_0064.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"96" + }, + { + "desc":"This section describes how to restore a single node instance from a backup.When you restore the DB instance from a backup file, a full backup file is downloaded from OBS ", + "product_code":"dds", + "title":"Restoring a Single Node Instance from a Backup", + "uri":"dds_03_0031.html", + "doc_type":"usermanual", + "p_code":"91", + "code":"97" }, { "desc":"This section describes how to download manual or automated backup files for local data backup or restoration.For details on how to log in to OBS Browser, see section Logg", @@ -491,8 +878,8 @@ "title":"Downloading Backup Files", "uri":"en-us_topic_backup_download.html", "doc_type":"usermanual", - "p_code":"50", - "code":"55" + "p_code":"91", + "code":"98" }, { "desc":"This section describes how to delete manual backups to release the storage space.The deletion operation is irreversible. Exercise caution when performing this operation.B", @@ -500,287 +887,197 @@ "title":"Deleting a Manual Backup", "uri":"dds_03_0008.html", "doc_type":"usermanual", - "p_code":"50", - "code":"56" + "p_code":"91", + "code":"99" }, { - "desc":"This section guides you on how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release sto", + "desc":"This section describes how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release storage", "product_code":"dds", "title":"Deleting an Automated Backup", "uri":"dds_03_0009.html", "doc_type":"usermanual", - "p_code":"50", - "code":"57" + "p_code":"91", + "code":"100" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Parameter Group", + "title":"Parameter Template Management", "uri":"dds_03_0010.html", "doc_type":"usermanual", - "p_code":"41", - "code":"58" + "p_code":"", + "code":"101" }, { - "desc":"DB parameter groups act as a container for engine configuration values that are applied to one or more DB instances. This section guides you on how to create a parameter ", + "desc":"DB parameter templates act as a container for engine configuration values that are applied to one or more DB instances.DDS does not share parameter template quotas with R", "product_code":"dds", - "title":"Creating a Parameter Group", + "title":"Creating a Parameter Template", "uri":"en-us_topic_parameter_group.html", "doc_type":"usermanual", - "p_code":"58", - "code":"59" + "p_code":"101", + "code":"102" }, { - "desc":"This section guides you on how to edit parameters in the parameter groups that you have created to meet your service requirements and achieve optimal performance.Default ", + "desc":"You can modify parameters in custom parameter templates as needed to get the most out of DDS performance.You can modify parameters in either of the following ways:Directl", "product_code":"dds", - "title":"Editing a Parameter Group", + "title":"Modifying a Parameter Template", "uri":"en-us_topic_configuration.html", "doc_type":"usermanual", - "p_code":"58", - "code":"60" + "p_code":"101", + "code":"103" }, { - "desc":"This section guides you on how to compare two parameter groups of the same node type and DB engine version to know their current settings.If the settings of the two param", + "desc":"You can view the change history of a parameter template.In a newly exported or created parameter template, the change history is blank.You can apply the parameter templat", "product_code":"dds", - "title":"Comparing Two Parameter Groups", + "title":"Viewing Parameter Change History", + "uri":"dds_03_0110.html", + "doc_type":"usermanual", + "p_code":"101", + "code":"104" + }, + { + "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to other instances by referring to Applying a Para", + "product_code":"dds", + "title":"Exporting a Parameter Template", + "uri":"dds_03_0111.html", + "doc_type":"usermanual", + "p_code":"101", + "code":"105" + }, + { + "desc":"This section describes how to compare two parameter templates of the same node type and DB engine version.If their settings are different, the parameter names and values ", + "product_code":"dds", + "title":"Comparing Parameter Templates", "uri":"dds_03_0012.html", "doc_type":"usermanual", - "p_code":"58", - "code":"61" + "p_code":"101", + "code":"106" }, { - "desc":"This section guides you on how to replicate a parameter group you created and assign it a name different from that of original group.Parameter Group Name: specifies the p", + "desc":"You can replicate a parameter template you have created.Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones", "product_code":"dds", - "title":"Replicating a Parameter Group", + "title":"Replicating a Parameter Template", "uri":"dds_03_0013.html", "doc_type":"usermanual", - "p_code":"58", - "code":"62" + "p_code":"101", + "code":"107" }, { - "desc":"After a DB instance is created, you can change the parameter group associated with the DB instance to achieve optimal performance. The parameter group associated with the", + "desc":"This section describes how to reset all parameters in a parameter template you create to the default settings as needed.Resetting a parameter template will restore all pa", "product_code":"dds", - "title":"Changing Associated Parameter Group", - "uri":"dds_03_0014.html", - "doc_type":"usermanual", - "p_code":"58", - "code":"63" - }, - { - "desc":"This section guides you on how to reset all parameters in a parameter group you create to the default settings as needed.Resetting the parameter group will restore the de", - "product_code":"dds", - "title":"Resetting a Parameter Group", + "title":"Resetting a Parameter Template", "uri":"dds_03_0015.html", "doc_type":"usermanual", - "p_code":"58", - "code":"64" + "p_code":"101", + "code":"108" }, { - "desc":"The section describes how to modify the description of the parameter group you created so that you can distinguish and identify parameter groups.", + "desc":"Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances or target node", "product_code":"dds", - "title":"Changing a Parameter Group Description", + "title":"Applying a Parameter Template", + "uri":"dds_03_0014.html", + "doc_type":"usermanual", + "p_code":"101", + "code":"109" + }, + { + "desc":"An application record contains information about performed apply operations. You can view the application records of a parameter template.Click Default Templates. Locate ", + "product_code":"dds", + "title":"Viewing Application Records of a Parameter Template", + "uri":"dds_03_0113.html", + "doc_type":"usermanual", + "p_code":"101", + "code":"110" + }, + { + "desc":"The section describes how to modify the description of a parameter template you created so that you can distinguish and identify parameter templates.", + "product_code":"dds", + "title":"Modifying the Description of a Parameter Template", "uri":"dds_03_0044.html", "doc_type":"usermanual", - "p_code":"58", - "code":"65" + "p_code":"101", + "code":"111" }, { - "desc":"This section guides you on how to delete a parameter group. The following parameter groups cannot be deleted.Default parameter groupsParameter groups associated with DB i", + "desc":"You can delete a custom parameter template that is no longer used.Default parameter templates and parameter templates applied to instances cannot be deleted.Deleted param", "product_code":"dds", - "title":"Deleting a Parameter Group", + "title":"Deleting a Parameter Template", "uri":"dds_03_0016.html", "doc_type":"usermanual", - "p_code":"58", - "code":"66" + "p_code":"101", + "code":"112" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Storage", - "uri":"dds_03_0017.html", - "doc_type":"usermanual", - "p_code":"41", - "code":"67" - }, - { - "desc":"This section guides you on how to add nodes to a DB instance.You can add nodes when the instance status is Available, Deleting backup, or Checking restoration.A DB instan", - "product_code":"dds", - "title":"Adding Cluster Instance Nodes", - "uri":"en-us_topic_increase_nodes.html", - "doc_type":"usermanual", - "p_code":"67", - "code":"68" - }, - { - "desc":"This section guides you on how to revert nodes that fail to be added.During reversal, the node status is Deleting node. This process takes about 1 to 3 minutes.During del", - "product_code":"dds", - "title":"Reverting Cluster Instance Nodes", - "uri":"dds_03_0018.html", - "doc_type":"usermanual", - "p_code":"67", - "code":"69" - }, - { - "desc":"This section guides you on how to scale up the storage space of a DB instance to suit your service requirements.You can scale up a DB instance a maximum of eight times.Yo", - "product_code":"dds", - "title":"Scaling Up Storage Space", - "uri":"en-us_topic_increase_storage.html", - "doc_type":"usermanual", - "p_code":"67", - "code":"70" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Changing DB Instance Classes", - "uri":"dds_08_0001.html", - "doc_type":"usermanual", - "p_code":"41", - "code":"71" - }, - { - "desc":"This section guides you on how to change the CPU or memory of a cluster instance.A DB instance cannot be deleted when you are changing its CPU or memory.Instances can be ", - "product_code":"dds", - "title":"Changing the CPU or Memory of a Cluster DB Instance", - "uri":"en-us_topic_0104472218.html", - "doc_type":"usermanual", - "p_code":"71", - "code":"72" - }, - { - "desc":"This section guides you on how to change the CPU or memory of your replica set instance.A DB instance cannot be deleted when you are changing its CPU or memory.Instances ", - "product_code":"dds", - "title":"Changing the CPU or Memory of a Replica Set DB Instance", - "uri":"en-us_topic_0104721795.html", - "doc_type":"usermanual", - "p_code":"71", - "code":"73" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Security", - "uri":"dds_03_0019.html", - "doc_type":"usermanual", - "p_code":"41", - "code":"74" - }, - { - "desc":"You are advised to change administrator passwords periodically to prevent password cracking, ensuring system security. You cannot reset the administrator password under t", - "product_code":"dds", - "title":"Resetting the Administrator Password", - "uri":"en-us_topic_reset_password.html", - "doc_type":"usermanual", - "p_code":"74", - "code":"75" - }, - { - "desc":"This section guides you on how to modify the database port to ensure system security. The database port cannot be changed when the instance is in any of the following sta", - "product_code":"dds", - "title":"Changing the Database Port", - "uri":"en-us_topic_change_database_port.html", - "doc_type":"usermanual", - "p_code":"74", - "code":"76" - }, - { - "desc":"This section guides you on how to change the security group of a DB instance. If any of the following operations is in progress, do not change the security group:Adding n", - "product_code":"dds", - "title":"Changing a Security Group", - "uri":"en-us_topic_change_security_group.html", - "doc_type":"usermanual", - "p_code":"74", - "code":"77" - }, - { - "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", - "product_code":"dds", - "title":"Tag", - "uri":"dds_03_0023.html", - "doc_type":"usermanual", - "p_code":"41", - "code":"78" - }, - { - "desc":"This section describes how to view the progress and result of asynchronous tasks on the Task Center page.Currently, only the following tasks can be viewed:Creating a clus", + "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", "product_code":"dds", "title":"Task Center", "uri":"dds_03_0040.html", "doc_type":"usermanual", - "p_code":"41", - "code":"79" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Monitoring", - "uri":"dds_03_0024.html", - "doc_type":"usermanual", "p_code":"", - "code":"80" + "code":"113" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Interconnected with Cloud Eye", + "title":"Monitoring and Alarm Reporting", "uri":"dds_03_0025.html", "doc_type":"usermanual", - "p_code":"80", - "code":"81" + "p_code":"", + "code":"114" }, { - "desc":"Table 1 lists the DB instance monitoring metrics.DB instance monitoring metricsMetricsUnitCOMMAND Statements per SecondCount/sDELETE Statements per SecondCount/sINSERT St", + "desc":"Cloud Eye monitors DDS instance metrics. You can obtain the monitoring metrics of DDS on the management console.Monitored data requires a period of time for transmission ", + "product_code":"dds", + "title":"Viewing DDS Metrics", + "uri":"dds_03_0076.html", + "doc_type":"usermanual", + "p_code":"114", + "code":"115" + }, + { + "desc":"This section describes metrics reported by Document Database Service (DDS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye", "product_code":"dds", "title":"DDS Metrics", "uri":"dds_03_0026.html", "doc_type":"usermanual", - "p_code":"81", - "code":"82" + "p_code":"114", + "code":"116" }, { - "desc":"You can set DDS alarm rules to customize the monitored objects and notification policies. Then, you can learn DDS running status in a timely manner.The DDS alarm rules in", + "desc":"You can enable the alarm reporting function in one click. After alarms are triggered, Simple Message Notification (SMN) can send notifications to specified cloud account.", "product_code":"dds", "title":"Setting Alarm Rules", "uri":"dds_03_0027.html", "doc_type":"usermanual", - "p_code":"81", - "code":"83" - }, - { - "desc":"Cloud Eye monitors DDS running statuses. You can obtain the monitoring metrics of DDS on the management console.Monitored data requires a period of time for transmission ", - "product_code":"dds", - "title":"Viewing DDS Metrics", - "uri":"dds_03_0078.html", - "doc_type":"usermanual", - "p_code":"81", - "code":"84" + "p_code":"114", + "code":"117" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Interconnecting with CTS", + "title":"Auditing", "uri":"dds_03_0028.html", "doc_type":"usermanual", - "p_code":"80", - "code":"85" + "p_code":"", + "code":"118" }, { - "desc":"With CTS, you can record operations associated with DDS for later query, audit, and backtrack operations.", + "desc":"With Cloud Trace Service (CTS), you can record operations associated with DDS for later query, audit, and backtrack operations.ddsAddTag and ddsDeleteTag are respectively", "product_code":"dds", "title":"Key Operations Recorded by CTS", "uri":"dds_03_0029.html", "doc_type":"usermanual", - "p_code":"85", - "code":"86" + "p_code":"118", + "code":"119" }, { - "desc":"After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.This section describ", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Querying Traces", - "uri":"dds_03_0032.html", + "title":"Log Management", + "uri":"dds_03_0024.html", "doc_type":"usermanual", - "p_code":"85", - "code":"87" + "p_code":"", + "code":"120" }, { "desc":"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 proble", @@ -788,17 +1085,26 @@ "title":"Error Log", "uri":"en-us_topic_error_log.html", "doc_type":"usermanual", - "p_code":"80", - "code":"88" + "p_code":"120", + "code":"121" }, { - "desc":"Slow query logs record statements whose execution period exceeds the value of slowms (100 ms by default), allowing you identify and optimize slowly executed statements.Lo", + "desc":"Slow query logs record statements whose execution period exceeds the value of operationProfiling.slowOpThresholdMs (100 ms by default). With slow query logs, you can iden", "product_code":"dds", "title":"Slow Query Log", "uri":"en-us_topic_slow_query_log.html", "doc_type":"usermanual", - "p_code":"80", - "code":"89" + "p_code":"120", + "code":"122" + }, + { + "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. Every cloud service is responsible for managing their own tags while T", + "product_code":"dds", + "title":"Tag Management", + "uri":"dds_03_0023.html", + "doc_type":"usermanual", + "p_code":"", + "code":"123" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -807,25 +1113,25 @@ "uri":"dds_faq_0100.html", "doc_type":"usermanual", "p_code":"", - "code":"90" + "code":"124" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Common FAQs", + "title":"Product Consulting", "uri":"dds_faq_0101.html", "doc_type":"usermanual", - "p_code":"90", - "code":"91" + "p_code":"124", + "code":"125" }, { - "desc":"FailoverDDS uses multiple mongos, replica sets, and shards to ensure data reliability. When a mongos is faulty, the other mongos takes over services immediately to ensure", + "desc":"Precautions after applying for DDS:After purchasing DDS DB instances, you do not need to perform basic database O&M operations, such as HA and security patches. You need ", "product_code":"dds", "title":"What Precautions Should Be Taken When Using DDS?", "uri":"dds_faq_0001.html", "doc_type":"usermanual", - "p_code":"91", - "code":"92" + "p_code":"125", + "code":"126" }, { "desc":"Formula for a DDS DB instance availability:DDS DB instance availability = (1 – Failure duration/Total service duration) × 100%.", @@ -833,17 +1139,8 @@ "title":"What Is the Availability of DDS DB Instances?", "uri":"dds_faq_0002.html", "doc_type":"usermanual", - "p_code":"91", - "code":"93" - }, - { - "desc":"You do not need a template to create DDS DB instances. When you create a DB instance, DDS provides different DB instance specifications which are similar to templates.", - "product_code":"dds", - "title":"Can I Use a Template to Create DDS DB Instances?", - "uri":"dds_faq_0003.html", - "doc_type":"usermanual", - "p_code":"91", - "code":"94" + "p_code":"125", + "code":"127" }, { "desc":"No. Your DDS DB instances and resources are isolated from others.", @@ -851,17 +1148,17 @@ "title":"Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?", "uri":"dds_faq_0004.html", "doc_type":"usermanual", - "p_code":"91", - "code":"95" + "p_code":"125", + "code":"128" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Management FAQs", + "title":"Database Performance", "uri":"dds_faq_0102.html", "doc_type":"usermanual", - "p_code":"90", - "code":"96" + "p_code":"124", + "code":"129" }, { "desc":"You can view the slow query logs to check whether any slowly executed SQL queries exist and view the performance characteristics of queries (if any) to locate the cause o", @@ -869,8 +1166,8 @@ "title":"What Should I Do If My Query Is Slow?", "uri":"dds_faq_0005.html", "doc_type":"usermanual", - "p_code":"96", - "code":"97" + "p_code":"129", + "code":"130" }, { "desc":"The delay for primary/secondary synchronization cannot be calculated using a formula. The delay is affected by the following factors:Network communication statusTransacti", @@ -878,8 +1175,17 @@ "title":"What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?", "uri":"dds_faq_0006.html", "doc_type":"usermanual", - "p_code":"96", - "code":"98" + "p_code":"129", + "code":"131" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Creation and Deletion", + "uri":"dds_faq_0103.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"132" }, { "desc":"DDS does not delete or perform any operations on any user data. If this problem occurs, check whether a misoperation has been performed. Restore the data using backup fil", @@ -887,8 +1193,8 @@ "title":"Why Is Data Missing from My Database?", "uri":"dds_faq_0007.html", "doc_type":"usermanual", - "p_code":"96", - "code":"99" + "p_code":"132", + "code":"133" }, { "desc":"If your cloud account is deleted, both your automated and manual backups are deleted.", @@ -896,71 +1202,35 @@ "title":"Will My Backups Be Deleted If I Delete My Cloud Account?", "uri":"dds_faq_0008.html", "doc_type":"usermanual", - "p_code":"96", - "code":"100" - }, - { - "desc":"Yes. Adding shards does not affect the existing shards. Services are still available.", - "product_code":"dds", - "title":"Are My DDS DB Instances Available When Scaling?", - "uri":"dds_faq_0009.html", - "doc_type":"usermanual", - "p_code":"96", - "code":"101" - }, - { - "desc":"Yes. DDS can perform write operations only on the primary node in a replica set. You can configure DDS to perform read operations on the secondary node to split read and ", - "product_code":"dds", - "title":"Does DDS Support Read/Write Splitting?", - "uri":"dds_faq_0010.html", - "doc_type":"usermanual", - "p_code":"96", - "code":"102" + "p_code":"132", + "code":"134" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Connection and Access FAQs", + "title":"Database Connection", "uri":"dds_faq_0104.html", "doc_type":"usermanual", - "p_code":"90", - "code":"103" + "p_code":"124", + "code":"135" }, { - "desc":"You can access the DDS DB instance using the following methods:Create a DDS DB instance and an ECS in the same VPC to enable the ECS to access the instance.If the DDS DB ", - "product_code":"dds", - "title":"Can an External Server Access the DDS DB Instance?", - "uri":"dds_faq_0011.html", - "doc_type":"usermanual", - "p_code":"103", - "code":"104" - }, - { - "desc":"The number of DDS database connections indicates the number of applications that can be simultaneously connected to the database. Generally, it indicates the number of co", + "desc":"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 maximu", "product_code":"dds", "title":"What Is the Number of DDS Database Connections?", "uri":"dds_faq_0012.html", "doc_type":"usermanual", - "p_code":"103", - "code":"105" + "p_code":"135", + "code":"136" }, { - "desc":"Perform the following steps to identify the problem: The following uses the cluster instance as an example.If they are in the same VPC, go to 2.If they are in different V", + "desc":"Perform the following steps to identify the problem:If yes, go to 3.If no, configure the VPC peering connection. For details, see \"VPC Peering Connection\" in Virtual Priv", "product_code":"dds", - "title":"What Should I Do If the ECS Cannot Connect to a DDS DB Instance?", + "title":"What Should I Do If an ECS Cannot Connect to a DDS DB Instance?", "uri":"dds_faq_0013.html", "doc_type":"usermanual", - "p_code":"103", - "code":"106" - }, - { - "desc":"Identify a DDS DB instance connection failure caused by a client problem from the following aspects.ECS Security PolicyIn Windows, check whether the DDS port is enabled i", - "product_code":"dds", - "title":"What Should I Do If a Database Client Problem Causes a Connection Failure?", - "uri":"dds_faq_0014.html", - "doc_type":"usermanual", - "p_code":"103", - "code":"107" + "p_code":"135", + "code":"137" }, { "desc":"Check whether the following problems occur on the DDS database. Check the following one at a time.The maximum number of connections is reached.Solution: Use the Cloud Eye", @@ -968,35 +1238,8 @@ "title":"What Should I Do If a DDS Server Problem Causes a Connection Failure?", "uri":"dds_faq_0015.html", "doc_type":"usermanual", - "p_code":"103", - "code":"108" - }, - { - "desc":"Ensure that the ECS where in which your applications are located is in the same VPC and subnet as the DDS DB instance. If the ECS and the DDS DB instance are in different", - "product_code":"dds", - "title":"How Can My Applications Access a DDS DB Instance in a VPC?", - "uri":"dds_faq_0016.html", - "doc_type":"usermanual", - "p_code":"103", - "code":"109" - }, - { - "desc":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", - "product_code":"dds", - "title":"Do Applications Need to Support Automatic Reconnecting to the DDS Database?", - "uri":"dds_faq_0017.html", - "doc_type":"usermanual", - "p_code":"103", - "code":"110" - }, - { - "desc":"For details on how to create and log in to an ECS, see \"Creating and Logging In to a Windows ECS\" or \"Creating and Logging In to a Linux ECS\" in the Elastic Cloud Server ", - "product_code":"dds", - "title":"How Can I Create and Log In to an ECS?", - "uri":"dds_faq_0034.html", - "doc_type":"usermanual", - "p_code":"103", - "code":"111" + "p_code":"135", + "code":"138" }, { "desc":"MongoDB official website provides client installation packages for different OSs. Download the official binary installation package at https://www.mongodb.com/download-ce", @@ -1004,89 +1247,44 @@ "title":"How Can I Install a MongoDB Client?", "uri":"dds_faq_0018.html", "doc_type":"usermanual", - "p_code":"103", - "code":"112" + "p_code":"135", + "code":"139" + }, + { + "desc":"This section describes how to obtain the Robo 3T installation package and install Robo 3T.For details on how to connect to a cluster instance, see Connecting to a Cluster", + "product_code":"dds", + "title":"How Do I Install Robo 3T?", + "uri":"dds_faq_0039.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"140" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Parameter and Metric FAQs", - "uri":"dds_faq_0108.html", + "title":"Database Usage", + "uri":"dds_faq_0105.html", "doc_type":"usermanual", - "p_code":"90", - "code":"113" + "p_code":"124", + "code":"141" }, { - "desc":"You need to focus on the CPU, memory, and storage space usage.You can configure DDS to report alarms as needed. If an alarm is reported, you can take proper measures to c", + "desc":"Yes. Adding shards does not affect the existing shards. Services are still available.", "product_code":"dds", - "title":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?", - "uri":"dds_faq_0019.html", + "title":"Are My DDS DB Instances Available When Scaling?", + "uri":"dds_faq_0009.html", "doc_type":"usermanual", - "p_code":"113", - "code":"114" + "p_code":"141", + "code":"142" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dds", - "title":"Network and Security FAQs", - "uri":"dds_faq_0110.html", + "title":"Database Storage", + "uri":"dds_faq_0107.html", "doc_type":"usermanual", - "p_code":"90", - "code":"115" - }, - { - "desc":"DDS allows you to set the VPC which DDS DB instances belong to, ensuring that the DDS DB instances are isolated from other services. In addition, the IAM service is provi", - "product_code":"dds", - "title":"What Security Protection Policies Does DDS Have?", - "uri":"dds_faq_0021.html", - "doc_type":"usermanual", - "p_code":"115", - "code":"116" - }, - { - "desc":"A VPC allows you to create virtual network environment in a private and isolated network to control the private IP address range, subnets, route tables, and network gatew", - "product_code":"dds", - "title":"Do I Need to Use DDS in a VPC?", - "uri":"dds_faq_0022.html", - "doc_type":"usermanual", - "p_code":"115", - "code":"117" - }, - { - "desc":"The VPC security group helps ensure the security of DDS in a VPC. In addition, ACL can be used to allow or reject I/O network traffic for each subnet. Use the internal se", - "product_code":"dds", - "title":"How Do I Ensure the Security of DDS in a VPC?", - "uri":"dds_faq_0023.html", - "doc_type":"usermanual", - "p_code":"115", - "code":"118" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dds", - "title":"Storage FAQs", - "uri":"dds_faq_0109.html", - "doc_type":"usermanual", - "p_code":"90", - "code":"119" - }, - { - "desc":"You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. You are advised to use the DDS backup function", - "product_code":"dds", - "title":"How Do I Back Up DDS to ECS?", - "uri":"dds_faq_0025.html", - "doc_type":"usermanual", - "p_code":"119", - "code":"120" - }, - { - "desc":"The automated backup retention period is 7 days by default. You can set a backup retention period from 1 to 732 days. There is no limit on the manual backup retention per", - "product_code":"dds", - "title":"How Long Does DDS Store Backup Data For?", - "uri":"dds_faq_0026.html", - "doc_type":"usermanual", - "p_code":"119", - "code":"121" + "p_code":"124", + "code":"143" }, { "desc":"The EVS is used for data storage of DDS DB instances. For details on the EVS, see Elastic Volume Service User Guide.The DDS DB instance backup data is stored in the OBS a", @@ -1094,8 +1292,8 @@ "title":"What Is the DDS DB Instance Storage Configuration?", "uri":"dds_faq_0028.html", "doc_type":"usermanual", - "p_code":"119", - "code":"122" + "p_code":"143", + "code":"144" }, { "desc":"If the storage space required by your applications exceeds the allowed maximum space allocated to you, you can do either of the following:Scale up storage space.Add shard", @@ -1103,17 +1301,17 @@ "title":"What Should I Do If My Data Exceeds the Database Storage Space of a DDS DB Instance?", "uri":"dds_faq_0029.html", "doc_type":"usermanual", - "p_code":"119", - "code":"123" + "p_code":"143", + "code":"145" }, { - "desc":"Both your common data (excluding backup data) and data required for ensuring DB instance proper running occupy the storage space on your purchased DDS DB instances. To en", + "desc":"The following types of data will occupy the storage space:User data except backupsData required for ensuring DB instance proper running occupy, such as system database da", "product_code":"dds", - "title":"Which Items Occupy the Storage Space on My Purchased DDS DB Instances?", + "title":"Which Items Occupy the Storage Space of DDS DB Instances?", "uri":"dds_faq_0030.html", "doc_type":"usermanual", - "p_code":"119", - "code":"124" + "p_code":"143", + "code":"146" }, { "desc":"The storage space you applied for will contain the system overhead required for inode, reserved block, and database operation.", @@ -1121,8 +1319,89 @@ "title":"What Overhead Does the Storage Space Have After I Applied for a DDS DB Instance?", "uri":"dds_faq_0031.html", "doc_type":"usermanual", - "p_code":"119", - "code":"125" + "p_code":"143", + "code":"147" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Backup and Restoration", + "uri":"dds_faq_0109.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"148" + }, + { + "desc":"You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. To ensure high data reliability and service as", + "product_code":"dds", + "title":"How Do I Back Up DDS Databases to an ECS?", + "uri":"dds_faq_0025.html", + "doc_type":"usermanual", + "p_code":"148", + "code":"149" + }, + { + "desc":"The automated backup retention period is 7 days by default. You can set a backup retention period from 1 to 732 days. There is no limit on the manual backup retention per", + "product_code":"dds", + "title":"How Long Does DDS Store Backup Data For?", + "uri":"dds_faq_0026.html", + "doc_type":"usermanual", + "p_code":"148", + "code":"150" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Network Security", + "uri":"dds_faq_0110.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"151" + }, + { + "desc":"DDS allows you to set the VPC which DDS DB instances belong to, ensuring that the DDS DB instances are isolated from other services. In addition, the IAM service is provi", + "product_code":"dds", + "title":"What Security Protection Policies Does DDS Have?", + "uri":"dds_faq_0021.html", + "doc_type":"usermanual", + "p_code":"151", + "code":"152" + }, + { + "desc":"The VPC security group helps ensure the security of DDS in a VPC. In addition, ACL can be used to allow or reject I/O network traffic for each subnet. Use the internal se", + "product_code":"dds", + "title":"How Do I Ensure the Security of DDS in a VPC?", + "uri":"dds_faq_0023.html", + "doc_type":"usermanual", + "p_code":"151", + "code":"153" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Resource Monitoring", + "uri":"dds_faq_0111.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"154" + }, + { + "desc":"You need to focus on the CPU, memory, and storage space usage.You can configure DDS to report alarms as needed. If an alarm is reported, you can take proper measures to c", + "product_code":"dds", + "title":"What DB Instance Monitoring Metrics Do I Need to Pay Attention To?", + "uri":"dds_faq_0019.html", + "doc_type":"usermanual", + "p_code":"154", + "code":"155" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dds", + "title":"Log Management", + "uri":"dds_faq_0112.html", + "doc_type":"usermanual", + "p_code":"124", + "code":"156" }, { "desc":"Logs and files listed in the following table occupy storage space.", @@ -1130,17 +1409,8 @@ "title":"Which Types of Logs and Files Occupy DDS DB Instance Storage Space?", "uri":"dds_faq_0032.html", "doc_type":"usermanual", - "p_code":"119", - "code":"126" - }, - { - "desc":"The following tables list the commands supported and restricted by DDS.", - "product_code":"dds", - "title":"Which Commands are Supported or Restricted by DDS?", - "uri":"dds_faq_0033.html", - "doc_type":"usermanual", - "p_code":"90", - "code":"127" + "p_code":"156", + "code":"157" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1149,7 +1419,7 @@ "uri":"dds_change_history.html", "doc_type":"usermanual", "p_code":"", - "code":"128" + "code":"158" }, { "desc":"For details about the glossaries in this document, see Glossary.", @@ -1158,6 +1428,6 @@ "uri":"dds_glossary.html", "doc_type":"usermanual", "p_code":"", - "code":"129" + "code":"159" } ] \ No newline at end of file diff --git a/docs/dds/umn/dds_01_0001.html b/docs/dds/umn/dds_01_0001.html index 9325c02fc..19e2b1c91 100644 --- a/docs/dds/umn/dds_01_0001.html +++ b/docs/dds/umn/dds_01_0001.html @@ -6,7 +6,7 @@ diff --git a/docs/dds/umn/dds_01_0014.html b/docs/dds/umn/dds_01_0014.html index 78446f833..d5d5f9cf9 100644 --- a/docs/dds/umn/dds_01_0014.html +++ b/docs/dds/umn/dds_01_0014.html @@ -1,7 +1,7 @@

Database Engine and Version

-

Currently, DDS is compatible with MongoDB 3.2 and 3.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 is compatible with MongoDB 3.2, 3.4, 4.0, and 4.2 Community Edition and supports the WiredTiger storage engine, so you need to use a driver compatible with MongoDB 3.0 or later to access DDS.

diff --git a/docs/dds/umn/dds_01_0015.html b/docs/dds/umn/dds_01_0015.html index 99bdb9f92..3eea00821 100644 --- a/docs/dds/umn/dds_01_0015.html +++ b/docs/dds/umn/dds_01_0015.html @@ -1,11 +1,22 @@

Typical Application Scenarios

-
  • Mobile Apps and Maps

    DDS supports two-dimensional space indexes for mobile applications (Apps) and maps that have location query requests. In addition, the dynamic storage mode of DDS is suitable for storing heterogeneous data of multiple systems, meeting the requirements of this scenario.

    -
  • IoT

    Internet of Things (IoT) applications generate terabytes of data and have high requirements on data write performance and low requirements on data read performance. DDS provides high write performance and shard-based DB instances to meet IoT requirements.

    -
  • CMS

    Content management system (CMS) has a large amount of data and queries and the data is non-structured and diverse. DDS provides high performance Schema-free, GridFS, and shards to support CMS applications.

    -
  • Game Industry

    DDS provides schema-free to meet ever-changing requirements in the gaming industry, shortening R&D periods and reducing R&D costs.

    -
+

Games

Game players' information generated from game applications, such as players' equipment and bonus points, are stored in DDS databases. During peak hours, DDS cluster instances can handle large amounts of concurrent requests. DDS cluster and replica set provide high availability to ensure the stable running of games in high-concurrency scenarios.

+

In addition, DDS is compatible with MongoDB and provides the non-schema mode, which frees you from changing table structure when the game play mode changes. DDS can totally meet the flexible gaming requirements. You can store structured data with fixed patterns in RDS, services with flexible patterns in DDS, and hot data in Distributed Cache Service (DCS) to facilitate access to service data and reduce data storage costs.

+

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.

+

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:

+
  • High Write Performance: DDS sharded cluster provides high write performance to meet the requirements of terabyte-scale databases.
  • High Performance and Scalability: DDS supports applications with high QPS rates, and its sharding architecture can be scaled in or out to flexibly cope with application changes.
+
+

Internet

DDS replica set uses the three-node HA architecture. Three data nodes form an anti-affinity group and are deployed on different physical servers to automatically synchronize data. The primary and secondary nodes provide services. Each node has a private IP address and works with Driver to allocate read workloads.

+

Many organizations need to process and store data into the TB range, requiring data to be written to databases in real time and dynamic analysis capabilities in big data computing.

+

Advantages:

+
  • MapReduce: With a complete data analysis utility, you can query statements or scripts, and distribute requests to DDS.
  • Excellent Scalability: DDS DB instances can be scaled up to support growing services and data volumes in content management systems.
+
diff --git a/docs/dds/umn/dds_01_0016.html b/docs/dds/umn/dds_01_0016.html index c9a77cd14..e5a3dedfd 100644 --- a/docs/dds/umn/dds_01_0016.html +++ b/docs/dds/umn/dds_01_0016.html @@ -1,26 +1,55 @@

Related Services

-

ECS

ECS provides DDS with elastic computing resources. DDS needs to apply for resources from ECS to build a running environment for DB instances.

-

For more information, see the Elastic Cloud Server User Guide.

-
-

EVS

Elastic Volume Service (EVS) provides DDS with elastic storage resources. DDS needs to apply for resources from EVS to build a running environment for DB instances.

-

For more information, see the Elastic Volume Service User Guide.

-
-

VPC

Virtual Private Cloud (VPC) provides DDS with elastic network resources and implements network isolation and access control for your DB instances.

-

For more information, see the Virtual Private Cloud User Guide.

-
-

OBS

OBS stores your DDS DB instance backup files.

-

For more information, see the Object Storage Service User Guide.

-
-

Cloud Eye

Cloud Eye serves as a monitoring platform, monitoring DDS resources for you. Cloud Eye supports multiple alarm rules to ensure timely pre-warning and normal service running.

-

For more information, see the Cloud Eye User Guide.

-
-

IAM

Identity and Access Management (IAM) provides the permission management function for DDS.

-

For more information, see the Identity and Access Management User Guide.

-
-

CTS

Cloud Trace Service (CTS) records operations related to DDS, facilitating your further queries, audits, and retrievals.

-

For more information, see the Cloud Trace Service User Guide.

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Related services

Service Name

+

Function

+

Elastic Cloud Service (ECS)

+

ECS provides DDS with elastic computing resources and a running environment for DB instances.

+

Virtual Private Cloud (VPC)

+

VPC provides DDS with elastic network resources and implements network isolation and access control for your DB instances.

+

Object Storage Service (OBS)

+

OBS stores your DDS DB instance backup files.

+

Cloud Eye

+

Cloud Eye serves as a monitoring platform, monitoring DDS resources for you in real time. It reports alarms and issues warnings promptly to ensure that services are running properly.

+

Identity and Access Management (IAM)

+

IAM provides the permission management function for DDS.

+

Cloud Trace Service (CTS)

+

CTS records operations related to DDS, facilitating your further queries, audits, and retrievals.

+

Data Replication Service (DRS)

+

DRS smoothly migrates databases to the cloud. Source databases remain operational during migration, minimizing downtime and impact.

+

Key Management Service (KMS)

+

KMS is a secure, reliable, and easy-to-use cloud service that helps users create, manage, and protect keys in a centralized manner.

+
diff --git a/docs/dds/umn/dds_01_0017.html b/docs/dds/umn/dds_01_0017.html index 800a4d737..e5c11f3bd 100644 --- a/docs/dds/umn/dds_01_0017.html +++ b/docs/dds/umn/dds_01_0017.html @@ -1,7 +1,7 @@

User Permissions

-

DDS provides two types of user permissions by default: user management and resource management.

+

IAM provides two types of user permissions by default: user management and resource management.

  • User management refers to the management of users, user groups, and user group rights.
  • Resource management refers to the control operations that can be performed by users on cloud service resources.

For details, see Permissions.

diff --git a/docs/dds/umn/dds_01_0019.html b/docs/dds/umn/dds_01_0019.html new file mode 100644 index 000000000..b5460b304 --- /dev/null +++ b/docs/dds/umn/dds_01_0019.html @@ -0,0 +1,724 @@ + + +

Permissions Management

+

If you need to assign different permissions to employees in your enterprise to access your DDS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your resources.

+

With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use DDS resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DDS resources.

+

If your account does not need individual IAM users for permissions management, you may skip over this topic.

+

IAM can be used free of charge. You pay only for the resources in your account.

+

DDS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

+

DDS is a project-level service deployed and accessed in specific physical regions. To assign GaussDB NoSQL permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing DDS, users need to switch to a region where they have been authorized to use DDS.

+

You can grant users permissions by using roles and policies.

+
  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DDS users only the permissions for managing a certain type of resources.
+

Table 1 lists all the system-defined roles and policies supported by DDS.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 System-defined roles and policies supported by DDS

Policy Name/System Role

+

Description

+

Type

+

Dependency

+

DDS FullAccess

+

All operations on DDS.

+

System-defined policy

+

None

+

DDS ReadOnlyAccess

+

Read-only permissions for DDS resources. Users granted these permissions can only view DDS data.

+

System-defined policy

+

None

+

DDS ManageAccess

+

DBA permissions on DDS except the DDS DB instance deletion operations.

+

System-defined policy

+

None

+

DDS Administrator

+

DDS administrator, who has all permissions of the service.

+

System-defined role

+

The Tenant Guest and Tenant Administrator roles need to be assigned in the same project.

+
+
+

Table 2 lists the common operations supported by each system-defined policy or role of DDS. Select the policies or roles as required.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Common operations supported by the DDS system policy

Operation

+

DDS FullAccess

+

DDS ReadOnlyAccess

+

DDS ManageAccess

+

DDS Administrator

+

Creating an instance

+

√

+

x

+

√

+

√

+

Querying DB instances

+

√

+

√

+

√

+

√

+

Deleting a DB instance

+

√

+

x

+

x

+

√

+

Restarting a DB instance

+

√

+

x

+

√

+

√

+

Performing a primary/secondary switchover

+

√

+

x

+

√

+

√

+

Modifying the port

+

√

+

x

+

√

+

√

+

Resetting a password

+

√

+

x

+

√

+

√

+

Modified SSL

+

√

+

x

+

√

+

√

+

Modifying a security group

+

√

+

x

+

√

+

√

+

Binding and unbinding an EIP

+

√

+

x

+

√

+

√

+

Scaling up storage space

+

√

+

x

+

√

+

√

+

Changing DB instance classes

+

√

+

x

+

√

+

√

+

Adding nodes

+

√

+

x

+

√

+

√

+

Deleting the node that fails to be added

+

√

+

x

+

×

+

√

+

Modifying an automated backup policy

+

√

+

x

+

√

+

√

+

Renaming a DB instance

+

√

+

x

+

√

+

√

+

Changing a private IP address

+

√

+

x

+

√

+

√

+

Changing the parameter template associated with the node in a DB instance

+

√

+

x

+

√

+

√

+

Showing original slow logs

+

√

+

x

+

√

+

√

+

Enabling or disabling local log auditing

+

√

+

x

+

√

+

√

+

Downloading audit logs

+

√

+

x

+

√

+

√

+

Deleting audit logs

+

√

+

x

+

×

+

√

+

Downloading a backup file

+

√

+

x

+

√

+

√

+

Creating a manual backup

+

√

+

x

+

√

+

√

+

Querying the backup list

+

√

+

√

+

√

+

√

+

Restoring data to a new DB instance

+

√

+

x

+

√

+

√

+

Restoring to an existing DB instance

+

√

+

x

+

√

+

√

+

Deleting a backup

+

√

+

x

+

×

+

√

+

Creating a parameter template

+

√

+

x

+

√

+

√

+

Viewing parameter templates

+

√

+

√

+

√

+

√

+

Modifying a parameter template

+

√

+

x

+

√

+

√

+

Deleting a parameter template

+

√

+

x

+

×

+

√

+

Task Center list

+

√

+

x

+

√

+

√

+
+
+

Table 3 lists common DDS operations and corresponding actions. You can refer to this table to customize permission policies.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 Common Operations and actions

Operation

+

Actions

+

Description

+

Instance creation page

+
  • vpc:vpcs:list
  • vpc:subnets:get
  • vpc:securityGroups:get
+

The VPC, subnet, and security group are displayed on the instance creation page.

+

Creating an instance

+
  • dds:instance:create
  • vpc:vpcs:list
  • vpc:vpcs:get
  • vpc:subnets:get
  • vpc:securityGroups:get
  • vpc:ports:get
+

If the default VPC, subnet, and security group are used, the vpc:*:create permission must be configured.

+

To create an encrypted instance, configure the KMS Administrator permission for the project.

+

Querying DB instances

+

dds:instance:list

+

-

+

Querying details of a DB instance

+

dds:instance:list

+

If the VPC, subnet, and security group need to be displayed on the instance details page, add the vpc:*:get and vpc:*:list actions.

+

Exporting DB instance lists

+

dds:instance:list

+

If the VPC, subnet, and security group are required, add the vpc:*:get and vpc:*:list actions.

+

Deleting a DB instance

+

dds:instance:deleteInstance

+

When deleting a DB instance, delete the IP address on the data side.

+

Restarting a DB instance

+

dds:instance:reboot

+

-

+

Performing a primary/secondary switchover

+

dds:instance:switchover

+

-

+

Changing a port

+

dds:instance:modifyPort

+

-

+

Resetting a password

+

dds:instance:resetPasswd

+

-

+

Modified SSL

+

dds:instance:modifySSL

+

-

+

Modifying a security group

+

dds:instance:modifySecurityGroup

+

-

+

Binding an EIP

+

dds:instance:bindPublicIp

+

When binding an EIP, you need to query the created EIP.

+
  • Enterprise projects are not supported.
  • Fine-grained authentication is not supported.
+

Unbinding an EIP

+

dds:instance:unbindPublicIp

+
  • Enterprise projects are not supported.
  • Fine-grained authentication is not supported.
+

Scaling up storage space

+

dds:instance:extendVolume

+

-

+

Changing DB instance classes

+

dds:instance:modifySpec

+

-

+

Adding nodes

+
  • dds:instance:extendNode
  • vpc:vpcs:list
  • vpc:vpcs:get
  • vpc:subnets:get
  • vpc:securityGroups:get
  • vpc:ports:get
+

-

+

Deleting the node that fails to be added

+

dds:instance:extendNode

+

If the IP address has been created but the subsequent procedure fails, delete the IP address on the data side.

+

Modifying an automated backup policy

+

dds:instance:modifyBackupPolicy

+

-

+

Renaming a DB instance

+

dds:instance:modify

+

-

+

Changing a private IP address

+
  • dds:instance:modifyVIP
  • vpc:subnets:get
  • vpc:ports:get
+

Before changing the private IP address, query available IP addresses.

+

Changing the parameter template associated with the node in a DB instance

+

dds:instance:modifyParameter

+

-

+

Showing original slow logs

+

dds:instance:modifySlowLogPlaintextSwitch

+

-

+

Enabling or disabling local log auditing

+

dds:instances:modifyAuditLogSwitch

+

-

+

Downloading audit logs

+

dds:instances:downloadAuditLog

+

-

+

Deleting audit logs

+

dds:instance:deleteAuditLog

+

-

+

Downloading a backup file

+

dds:backup:download

+

-

+

Creating a Manual Backup

+

dds:instance:createManualBackup

+

-

+

Querying the backup list

+

dds:backup:list

+

-

+

Restoring data to a new DB instance

+
  • dds:backup:createInstanceFromBackup
  • vpc:vpcs:list
  • vpc:vpcs:get
  • vpc:subnets:get
  • vpc:securityGroups:get
  • vpc:ports:get
+

The KMS Administrator permission needs to be configured for the encrypted instance in the project.

+

Restoring to an existing DB instance

+

dds:backup:refreshInstanceFromBackup

+

-

+

Deleting a backup

+

dds:backup:delete

+

-

+

Creating a parameter template

+

dds:param:create

+

-

+

Viewing parameter templates

+

dds:param:list

+

-

+

Modifying a parameter template

+

dds:param:modify

+

-

+

Deleting a parameter template

+

dds:param:delete

+

-

+

Task Center list

+

dds:task:list

+

-

+
+
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/dds/umn/dds_01_0021.html b/docs/dds/umn/dds_01_0021.html index fe37b603d..5a1b2eda0 100644 --- a/docs/dds/umn/dds_01_0021.html +++ b/docs/dds/umn/dds_01_0021.html @@ -1,13 +1,14 @@

System Architecture

-

-
+
diff --git a/docs/dds/umn/dds_01_0022.html b/docs/dds/umn/dds_01_0022.html new file mode 100644 index 000000000..d0c0364c1 --- /dev/null +++ b/docs/dds/umn/dds_01_0022.html @@ -0,0 +1,69 @@ + + +

Constraints and Recommendations

+

To improve the stability and security of DB instances, there are some constraints on the use of DDS. For details, see Table 1.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Function constraints

Topic

+

Constraints

+

Connecting to a DB instance

+
  • When connecting to a DB instance over private networks, bind an EIP to the prepared ECS.
  • By default, DDS is not accessible from ECSs that are not in the same security group. If the ECS is not in the same security group, you need to add an inbound rule to enable access.
  • The default DDS port is 8635, but this port can be modified if necessary.
+

Deployment

+

ECS instances in which DB instances are deployed are not visible to you. Your applications can access the database only through an IP address and port.

+

Obtaining permissions of user rwuser

+

Only the rwuser user permissions are provided on the instance creation page.

+

For details about the related commands, see Which Commands are Supported or Restricted by DDS?

+

Setting database parameters

+

+

+

Most database parameters in the parameter templates you created can be modified. For details, see section Modifying a Parameter Template.

+

Migrating data

+

You can use multiple tools to migrate your data between databases, such as mongoexport and mongoimport. For details, see section Migrating Data.

+

Storage engine

+

DDS supports the WiredTiger storage engine.

+

Nodes

+

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

+

Restarting a DB instance or a node

+

DB instances cannot be restarted using commands. They must be restarted on the management console.

+

Viewing DDS backup files

+

DDS backups are saved in OBS buckets but these cannot be accessed directly. You can download and view the files on the DDS console. For details, see section Downloading Backup Files.

+
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/dds/umn/dds_01_0024.html b/docs/dds/umn/dds_01_0024.html index 622e42ee9..cffc4d246 100644 --- a/docs/dds/umn/dds_01_0024.html +++ b/docs/dds/umn/dds_01_0024.html @@ -2,77 +2,87 @@

DB Instance Specifications

DB instance specifications are listed in the following table.

-

DB instance specifications vary depending on the actual environment.

+

The DB instance specifications depend on service requirements.

+

You can change the maximum number of connections of a DB instance by modifying the net.maxIncomingConnections parameter. For details about how to change the parameter value, see Modifying a Parameter Template.

-

Cluster

For details about the cluster instance specifications, see Table 1 and Table 2.

+

Cluster

For details about the cluster instance specifications, see Table 1 and Table 2.

-
Table 1 config specifications

Number of vCPUs

+
- - + - - - + - -
Table 1 config specifications

CPU Type

Memory (GB)

+

vCPUs

Max. Number of Connections

+

Memory (GB)

+

Default Maximum Number of Connections

2

+

x86

4

+

2

1000

+

4

+

600
-
- -
- - - - - - - - - - - - - - - - - - - - - - -
Table 2 shard and mongos specifications

Number of vCPUs

-

Memory (GB)

-

Max. Number of Connections

-

1

-

4

-

400

-

2

-

8

-

400

-

4

-

16

-

1000

-

8

-

32

-

4000

-

16

-

64

-

8000

+

Kunpeng
-

Replica Set

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

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 shard and mongos specifications

vCPUs

+

Memory (GB)

+

Default Maximum Number of Connections

+

1

+

4

+

400

+

2

+

8

+

400

+

4

+

16

+

1000

+

8

+

32

+

4000

+

16

+

64

+

8000

+
+
+

Replica Set

The specifications supported by a replica set 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 mongos. For details, see Table 2.

diff --git a/docs/dds/umn/dds_01_0025.html b/docs/dds/umn/dds_01_0025.html new file mode 100644 index 000000000..a5785c03b --- /dev/null +++ b/docs/dds/umn/dds_01_0025.html @@ -0,0 +1,15 @@ + + +

Single Node Architecture

+

A single node instance, as its name suggests, contains only one node which can be accessed directly.

+

As a supplement to the cluster and replica set architectures, the single-node architecture applies to R&D, testing, and non-core data storage of enterprises. While not as robust as replica sets, the single node architecture can be a less expensive way to visualize O&M and provide elastic scaling.

+

A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see official documents.

+
+
Figure 1 Single node architecture
+
+
+
+
Parent topic: System Architecture
+
+
+ diff --git a/docs/dds/umn/dds_01_0026.html b/docs/dds/umn/dds_01_0026.html index e9e92ed52..b87231b82 100644 --- a/docs/dds/umn/dds_01_0026.html +++ b/docs/dds/umn/dds_01_0026.html @@ -1,101 +1,131 @@ -

Database Status

+

DB Instance Status

DB Instance Status

-
Table 1 Status and description

Status

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + +
Table 1 Status and description

Status

Description

+

Description

Available

+

Available

A DB instance is running properly.

+

A DB instance is running properly.

Abnormal

+

Abnormal

A DB instance is faulty.

+

A DB instance is faulty.

Creating

+

Creating

A DB instance is being created.

+

A DB instance is being created.

Creation failed

+

Creation failed

A DB instance fails to be created.

+

A DB instance fails to be created.

Restarting

+

Backing up

A DB instance is being restarted because of a customer request or a modification that requires restarting it for the modification to take effect.

+

An instance backup is being created.

Switchover in progress

+

Restarting

The primary and secondary nodes of a replica set instance are being switched.

+

A DB instance is being restarted because of a modification that requires restarting it for the modification to take effect.

Adding node

+

Switchover in progress

shards or mongos are being added to a DDS cluster instance.

+

The primary and standby nodes of the replica set instance or the primary and standby shards or configs of a cluster instance are being switched over.

Deleting node

+

Adding node

The node that failed to be added is being deleted.

+

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

Scaling up

+

Deleting node

The storage space of instance nodes is being expanded.

+

The node that failed to be added is being deleted.

Changing instance class

+

Scaling up

The CPU or memory of a DB instance is being changed.

+

The storage space of instance nodes is being expanded.

Backing up

+

Changing instance class

A backup file is being created.

+

The CPU or memory of a DB instance is being changed.

Checking restoration

+

Checking restoration

The backup of the current DB instance is being restored to a new DB instance.

+

The backup of the current DB instance is being restored to a new DB instance.

Switching SSL

+

Restoring

The SSL channel is being enabled or disabled.

+

The backup is being restored to the existing DB instance.

Changing private IP address

+

Restoration failed

The private IP address of a node is being changed.

+

Restoring to the existing DB instance failed.

Changing port

+

Switching SSL

The DB instance port is being changed.

+

The SSL channel is being enabled or disabled.

Changing a security group

+

Querying original slow query logs

The security group is being changed.

+

Show Original Log is being enabled or disabled.

+

Changing private IP address

+

The private IP address of a node is being changed.

+

Changing port

+

The DB instance port is being changed.

+

Changing a security group

+

The security group is being changed.

+

Enabling shard IP Address

+

The shard IP address is being enabled.

+

Enabling config IP Address

+

The config IP address is being enabled.

+

Changing the oplog size

+

The oplog size is being changed.
-

Parameter Group Status

+

Parameter Template Status

- diff --git a/docs/dds/umn/dds_01_0027.html b/docs/dds/umn/dds_01_0027.html index f68e61c16..f64cb103b 100644 --- a/docs/dds/umn/dds_01_0027.html +++ b/docs/dds/umn/dds_01_0027.html @@ -2,9 +2,9 @@

Regions and AZs

A region is a geographic area in which resources used by DDS are located.

-

Each region comprises one or more AZs and is completely isolated from other regions. AZs within the same region can communicate with one another through an internal network, while those in different regions cannot communicate with one another through an internal network.

-

Public cloud data centers are deployed worldwide. DDS applies to different regions. Provisioning DDS to specific regions can better meet user requirements. For example, applications can be designed to better meet specific user requirements or comply with local laws and other demands.

-

Each region contains many AZs where power and networks are physically isolated. AZs in the same region can communicate with each other over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults in other AZs. As a result, provisioning DDS in separate AZs protects your applications against local faults that occur in a single location. DDS supports the deployment of a replica set instance across three AZs. It means that the primary, secondary, and hidden nodes are deployed in three AZs for disaster recovery.

+

Each region comprises one or more AZs and is completely isolated from other regions. AZs within the same region can communicate with one another through an internal network.

+

Cloud service platform data centers are deployed worldwide. DDS applies to different regions. Provisioning DDS to specific regions can better meet user requirements. For example, applications can be designed to better meet specific user requirements or comply with local laws and other demands.

+

Each region contains many AZs where power and networks are physically isolated. AZs in the same region can communicate with each other over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults in other AZs. As a result, provisioning DDS in separate AZs protects your applications against local faults that occur in a single location. DDS allows you to deploy replica sets across three AZs for disaster recovery.

diff --git a/docs/dds/umn/dds_02_0001.html b/docs/dds/umn/dds_02_0001.html new file mode 100644 index 000000000..9cfbdf358 --- /dev/null +++ b/docs/dds/umn/dds_02_0001.html @@ -0,0 +1,46 @@ + + +

Connection Methods

+

You can access DDS over private or public networks.

+ +
Table 2 Status and description

Status

Description

+

Description
+ + + + + + + + + + + + + + + + +
Table 1 Connection methods

Method

+

IP Address

+

Scenario

+

Description

+

Private network

+

Private IP address

+

DDS provides a private IP address by default.

+
  • You are advised to use private IP address in following scenarios:
    • Your ECS instance is in the same VPC subnet as the DDS DB instance.
    • ECS subnet and DDS subnet are connected to each other by VPC peering.
    +
+
  • By default, DDS is not accessible from ECSs that are not in the same security group. If the ECS is not in the same security group, you need to add an inbound rule to enable access.
  • The default DDS port is 8635, but this port can be modified if necessary. You are advised to modify the port to ensure database security.
+

Secure and excellent performance

+

Public network

+

EIP

+
  • If your applications are running on an ECS that is in a different region from the one where the DB instance is located, you are advised to use an EIP to connect the ECS to your DDS DB instances.
  • If your applications are deployed on another cloud platform, EIP is recommended.
+
  • Low security
  • For faster transmission and improved security, you are advised to migrate your applications to an ECS that is in the same subnet as your DDS instance and use a private IP address to access the DDS instance.
+
+
+
+
+
+
Parent topic: Getting Started with Clusters
+
+
+ diff --git a/docs/dds/umn/dds_02_0002.html b/docs/dds/umn/dds_02_0002.html deleted file mode 100644 index b5d92f74c..000000000 --- a/docs/dds/umn/dds_02_0002.html +++ /dev/null @@ -1,65 +0,0 @@ - - -

Restrictions

-

To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.

- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 1 Function restrictions

Operation

-

Restrictions

-

Connecting to a DB instance through a client

-
  • To access a DDS DB instance which is not publicly accessible from an ECS, the instance must be in the same VPC subnet as the ECS.
  • By default, DDS cannot be accessed through an ECS in a different security group. You need to add an inbound rule to the DDS security group.
  • The default DDS port number is 8635. You can change it if you want to access DDS through another port.
-

Deployment

-

ECSs in which DB instances are deployed are not visible to you. Your applications can access the database only through an IP address and port.

-

Obtaining permissions of user rwuser

-

Only the rwuser user permissions are provided on the instance creation page.

-

For details about the related commands, see Which Commands are Supported or Restricted by DDS?

-

Setting database parameters

-

-

-

Most database parameters in the parameter groups you created can be modified. For details, see section Editing a Parameter Group.

-

-

Migrating data

-

You can use command line tools, including mongoexport and mongoimport, to migrate data. For details, see section Migrating Data.

-

Storage engine

-

The WiredTiger storage engine is supported.

-

Restarting a DB instance or a node

-

A DDS DB instance must be restarted on the DDS console.

-

Viewing DDS backup files

-

You can download and view the backup files on the DDS console. For details, see section Downloading Backup Files.

-
-
-
-
-
-
Parent topic: Getting Started with Clusters
-
-
- diff --git a/docs/dds/umn/dds_02_0003.html b/docs/dds/umn/dds_02_0003.html deleted file mode 100644 index b699e18d9..000000000 --- a/docs/dds/umn/dds_02_0003.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

Service Process

-

This section describes how to create a cluster instance, set a security group, and connect to a cluster instance.

-

Intended Audience

  • Users who create the DDS DB instance for the first time.
  • Users who need to perform the initial configuration after a DB instance is created.
  • Users who want to know how to connect to the DDS DB instances.
-
-

Process

The following describes the steps from creating a DB instance to using it.

-
Figure 1 Accessing DB instances from a public network
-
Figure 2 Accessing DB instances from a private network
-
-
-
-
-
Parent topic: Getting Started with Clusters
-
-
- diff --git a/docs/dds/umn/dds_02_0005.html b/docs/dds/umn/dds_02_0005.html deleted file mode 100644 index 49941c9b7..000000000 --- a/docs/dds/umn/dds_02_0005.html +++ /dev/null @@ -1,56 +0,0 @@ - - -

Setting a Security Group

-

Scenarios

This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.

-
-

Background Information

You can access a DDS DB instance in either of the following ways:

-
  • Public network
  • Internal network
-
-

Precautions

The default security group rule allows all outgoing data packets. ECSs and DDS DB instances can access each other in the same security group. After a security group is created, you can add security group rules to control the access from and to the DDS DB instances in the security group.

-

By default, a tenant can create a maximum of 500 security group rules. An excessive number of security group rules increases the network latency of the first packet. It is recommended that you add a maximum of 50 rules for each security group.

-

To access the DDS DB instances in a security group from external resources, create an inbound rule for the security group.

-
-

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click Service List. Under Network, click Virtual Private Cloud.
  4. In the navigation pane on the left, choose Access Control > Security Groups.
  5. On the Security Group page, click the security group name.
  6. On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
  7. Add a security group rule as prompted.

    -

    - - - - - - - - - - - - - - - - - -
    Table 1 Field description

    Parameter

    -

    Description

    -

    Value Example

    -

    Protocol

    -

    Specifies the network protocol. Allows all traffic or supports user-defined protocols, TCP, UDP, ICMP, and SSH.

    -

    TCP

    -

    Port

    -

    Specifies the port allowing the access to ECSs or external devices.

    -

    8635

    -

    Source/Destination

    -

    Specifies the supported IP address and security group.

    -
    • IP address: indicates that the security group rule takes effect in a specified IP address range.
      • xxx.xxx.xxx.xxx/32 (IPv4)
      • xxx.xxx.xxx.0/24 (subnet)
      • 0.0.0.0/0 (any IP address)
      -
    • Security group: indicates that this rule allows all IP addresses of ECSs to access DDS DB instances in the same specified security group.
    -
    • 192.168.10.0/24
    • default
    -
    -
    -

  8. Click OK.
-
-
-
-
-
Parent topic: Getting Started with Clusters
-
-
- diff --git a/docs/dds/umn/dds_02_0006.html b/docs/dds/umn/dds_02_0006.html index 618d02e16..d95dc95f7 100644 --- a/docs/dds/umn/dds_02_0006.html +++ b/docs/dds/umn/dds_02_0006.html @@ -1,25 +1,85 @@ -

Binding and Unbinding an EIP

-

Scenarios

You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:

-
  • Use a private IP address when:

    DDS provides a private IP address by default.

    -

    Your applications are deployed on an ECS in a region where your cluster instance is located.

    -
-
  • Use an EIP when:
    • Your applications are deployed on an ECS in a region separated from the region where your cluster instance is located.
    • Your applications are deployed on another cloud platform.
    -
+

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.

+

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.

-

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.
+

Prerequisites

  1. Bind an EIP to the cluster instance and set security group rules to ensure that the EIP can be accessed with the DB client application.
  2. Install the MongoDB client or Robo 3T.

    MongoDB client

    +
    1. For details on how to create and log in to an ECS, 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.
    2. Install the MongoDB client on the ECS.

      For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

      +

      If you use a connection address to connect to a cluster instance, download the MongoDB client of version later than 3.4.

      +
      +
    +

    Robo 3T

    +

    For details on how to install Robo 3T, see How Do I Install Robo 3T?

    +
  3. If SSL is enabled, download the SSL certificate on the DDS console.
    1. On the Instance Management page, click the target DB instance.
    2. In the navigation pane on the left, choose Connections.
    3. In the Basic Information area, click next to the SSL field.
    +

    The certificate can also be downloaded from the Node Information area on the Basic Information page.

    +
    +

    +
-

Binding an EIP

  1. On the Instance Management page, click the target cluster instance.
  2. In the navigation pane on the left, choose Connections.
  3. In the Basic Information area, locate the target mongos node and click Bind EIP in the Operation column.
  4. In the displayed dialog box, all EIPs in the unbound status 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.
  5. 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.

    +

    Connecting to a DB Instance Using Robo 3T (SSL)

    If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

    +
    +
    1. Run the installed Robo 3T. On the displayed dialog box, click Create.

      Figure 1 Connections
      +

    2. In the Connection Settings dialog box, set the parameters of the new connection.

      1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the DDS DB instance in the Address text box.
        Figure 2 Connection
        +
      2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the cluster instance.
        Figure 3 Authentication
        +
      3. On the SSL tab, upload the SSL certificate and select Allowed for Invalid Hostnames.
        Figure 4 SSL
        +
      4. Click Save.
      +

    3. On the MongoDB Connections page, click Connect to connect to the cluster instance.

      Figure 5 Connections
      +

    4. If the cluster instance is successfully connected, the page shown in Figure 6 is displayed.

      Figure 6 Connection succeeded

    -

    Unbinding an EIP

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

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

      +

      Connecting to a DB Instance Using Robo 3T (Non-SSL)

      If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

      +
      +
      1. Run the installed Robo 3T. On the displayed dialog box, click Create.

        Figure 7 Connections
        +

      2. In the Connection Settings dialog box, set the parameters of the new connection.

        1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the DDS DB instance in the Address text box.
          Figure 8 Connection
          +
        2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the cluster instance.
          Figure 9 Authentication
          +
        3. Click Save.
        +

      3. On the MongoDB Connections page, click Connect to connect to the cluster instance.

        Figure 10 Connections
        +

      4. If the cluster instance is successfully connected, the page shown in Figure 11 is displayed.

        Figure 11 Connection succeeded
        +

      +
      +

      Connecting to a DB Instance Using the MongoDB Client (SSL)

      If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

      +
      +
      1. On the Instance Management page, click the target DB instance.
      2. In the navigation pane on the left, choose Connections.
      3. In the Basic Information area, click next to the SSL field.
      4. Upload the root certificate to the ECS to be connected to the DB instance.

        The following describes how to upload the certificate to a Linux and Window ECS:

        +
        • In Linux, run the following command:
          scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
          • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
          • REMOTE_USER indicates the ECS OS user.
          • REMOTE_ADDRESS indicates the ECS address.
          • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
          +
          +
          +
        • In Windows, upload the root certificate using the remote connection tool.
        +

      5. Connect to the DB instance in the directory where the MongoDB client is located.

        • Method 1: Using standard parameters

          mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

          +

          Enter the database account password when prompted:

          +
          Enter password:
          +
        • Method 2: Using standard URI format

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

          +

          To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

          +
        +
        • A cluster instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection in a public network.
        • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
        +
        +
        • Connect to the instance using standard parameters. The following is an example command:

          mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

          +
        • Using standard URI format:

          mongo mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

          +
        +

      6. Check the connection result. If the following information is displayed, the connection is successful.

        mongos>
        +

      +
      +

      Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

      If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

      +
      +
      1. Connect to the DB instance in the directory where the MongoDB client is located.

        • Method 1: Using standard parameters

          mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

          +

          Enter the database account password when prompted:

          +
          Enter password:
          +
        • Method 2: Using standard URI format

          ./mongo mongodb://rwuser:<password>@<DB_HOST>:<DB_PORT>/test?authSource=admin

          +

          To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

          +
        +
        • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
        +
        +
        • Connect to the instance using standard parameters. The following is an example command:

          mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

          +
        • Using standard URI format:

          mongo mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin

          +
        +

      2. Check the connection result. If the following information is displayed, the connection is successful.

        mongos>

    diff --git a/docs/dds/umn/dds_02_0007.html b/docs/dds/umn/dds_02_0007.html deleted file mode 100644 index c83c6a233..000000000 --- a/docs/dds/umn/dds_02_0007.html +++ /dev/null @@ -1,21 +0,0 @@ - - -

    Enabling or Disabling SSL

    -

    Scenarios

    DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.

    -
    • If SSL is enabled, you can connect to a database using SSL. For details, see SSL Connection.
    • If SSL is disabled, you can connect to the database using a common connection. For details, see Common Connection.
    -

    Enabling or disabling SSL will cause DB instance restart. Exercise caution when you perform this operation.

    -
    -
    -

    Enabling SSL

    1. On the Instance Management page, click the target DB instance.
    2. In the DB Information area on the Basic Information page, click to enable SSL in the SSL field.

      Alternatively, in the navigation pane on the left, choose Connections. In the Basic Information area, click next to the SSL field.

      -

    3. In the displayed dialog box, click Yes.
    4. In the Basic Information area, view the modification result.
    -
    -

    Disabling SSL

    1. On the Instance Management page, click the target DB instance.
    2. In the DB Information area on the Basic Information page, click to enable SSL in the SSL field.

      Alternatively, in the navigation pane on the left, choose Connections. In the Basic Information area, click next to the SSL field.

      -

    3. In the displayed dialog box, click Yes.
    4. In the Basic Information area, view the modification result.
    -
    -
    -
    -
    -
    Parent topic: Connecting to a Cluster Instance
    -
    -
    - diff --git a/docs/dds/umn/dds_02_0008.html b/docs/dds/umn/dds_02_0008.html deleted file mode 100644 index deef9e26e..000000000 --- a/docs/dds/umn/dds_02_0008.html +++ /dev/null @@ -1,242 +0,0 @@ - - -

    Creating a Cluster Instance

    -

    Scenarios

    This section describes how to create a DDS cluster instance of Community Edition on the DDS management console. DDS allows you to tailor your computing resources and storage space to your business needs.

    -

    You can use your account to create a maximum of 10 cluster instances. To create more cluster instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

    -
    -

    Procedure

    1. Log in to the DDS console.
    2. On the Instance Management page, click Create DB Instance.
    3. On the displayed page, configure parameters about DB instance specifications. Then, click Create Now.

      -

      - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      Table 1 Basic information

      Parameter

      -

      Description

      -

      Region

      -

      A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

      -
      NOTE:

      DB instances 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, 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 (_).

      -

      After the DB instance is created, you can change the DB instance name. For details, see section Modifying the DB Instance Name.

      -

      -

      -

      Database Type

      -

      Community Edition

      -

      DB Instance Type

      -

      Select Cluster.

      -

      A cluster instance includes three types of nodes: mongos, shard, and config. shard and config use the three-node replica set architecture to ensure high availability.

      -

      Compatible MongoDB Version

      -
      • 3.4
      • 3.2
      -

      Storage Engine

      -

      WiredTiger

      -

      AZ

      -

      A physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through the internal network. For details, see section Regions and AZs.

      -

      Disk Encryption

      -
      • Disable: Disable the encryption function.
      • Enable: 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 a DB instance is created, the disk encryption status and the key cannot be changed. Backup data stored on 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 2 Specifications

      Item

      -

      Description

      -

      mongos 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 the CPU or Memory of a Cluster DB Instance.

      -

      mongos quantity

      -

      The value ranges from 2 to 16. After a DB instance is created, you can add nodes. For details, see section Adding Cluster Instance Nodes.

      -

      mongos parameter group

      -

      Parameters in a mongos parameter group can be applied to mongos nodes. After a DB instance is created, you can change the parameter group of a node. For a parameter group created by users, you can modify the parameters in the parameter group to bring out the best performance.

      -

      -

      -

      For details, see Parameter Group.

      -

      -

      shard class

      -

      For details about the shard 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 the CPU or Memory of a Cluster DB Instance.

      -

      shard storage type

      -

      Ultra-high I/O: uses the SSD disk type.

      -

      shard storage space

      -

      The value ranges from 10 GB to 1,000 GB and must be a multiple of 10. After a DB instance is created, you can scale up its storage space. For details, see section Scaling Up Storage Space.

      -

      shard quantity

      -

      shard stores user data but cannot be accessed directly by you.

      -

      The value ranges from 2 to 16. After a DB instance is created, you can add nodes. For details, see section Adding Cluster Instance Nodes.

      -

      shard parameter group

      -

      Parameters in a shard parameter group can be applied to shard nodes. After a DB instance is created, you can change the parameter group of a node. For a parameter group created by users, you can modify the parameters in the parameter group to bring out the best performance.

      -

      -

      -

      For details, see Parameter Group.

      -

      -

      config class

      -

      config stores DB instance configurations but cannot be accessed directly by you. For details, see DB Instance Specifications.

      -

      config storage type

      -

      Ultra-high I/O: uses the SSD disk type.

      -

      config storage space

      -

      The storage space is 20 GB and cannot be scaled up.

      -

      config parameter group

      -

      Parameters in a config parameter group can be applied to config nodes. After a DB instance is created, you can change the parameter group of a node. For a parameter group created by users, you can modify the parameters in the parameter group to bring out the best performance.

      -

      -

      -

      For details, see Parameter Group.

      -

      -
      -
      - -
      - - - - - - - - - - - - - - - - -
      Table 3 Network

      Parameter

      -

      Description

      -

      VPC

      -

      The VPC to which a DB instance belongs isolates networks for different services. It allows user to manage and configure internal networks and change network configuration, simplifying network management. You need to create or select the required VPC. For details on how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide.

      -

      Subnet

      -

      A subnet provides dedicated network resources that are logically isolated from other networks, improving network security. After a DB instance is created, you can click the DB instance name and change the private IP address assigned by the subnet to the mongos node on the Basic Information page.

      -
      NOTE:

      Changing the private IP address of a node will invalidate the previous private IP address. If an EIP is bound to the node, do not unbind the EIP during the change of the private IP address. After the change, the new private IP address is bound to the EIP.

      -
      -

      Security Group

      -

      A security group controls access between DDS and other services for security.

      -
      NOTE:

      Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

      -
      -

      SSL

      -

      Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

      -

      You can enable SSL to improve data security. After a DB instance is created, you can connect to it in SSL mode. For details, see Connecting to a DB Instance Through a Client.

      -
      -
      - -
      - - - - - - - - - - - - - -
      Table 4 Database configuration

      Parameter

      -

      Description

      -

      Administrator

      -

      The default account is rwuser.

      -

      Administrator Password

      -

      The password is a string of 8 to 32 characters. It must be a combination of uppercase letters, lowercase letters, digits, and special characters. You can also use the following special characters: ~!@#%^*-_=+?

      -

      The system cannot save you password. Keep the password secure.

      -

      Confirm Password

      -

      The value of this parameter must be the same as the Administrator Password.

      -
      -
      - -
      - - - - - - - -
      Table 5 Tag

      Parameter

      -

      Description

      -

      Tags

      -

      Tags a DDS DB instance. This configuration is optional. Adding tags to DDS DB instances helps you better identify and manage them. Each DB instance can have up to 20 tags.

      -

      A tag is composed of a key-value pair.

      -
      • Key: Mandatory if the DB instance is going to be tagged
        • For each DB instance, each tag key is unique.
        • A tag key consists of a maximum of 36 characters.
        • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
        -
      • Value: Optional if the DB instance is going to be tagged
        • The value consists of a maximum of 43 characters.
        • The value can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
        -
      -

      After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag.

      -
      -
      -

      DB instance performance is determined by the configurations you set during its creation, including the node class and storage space.

      -
      -

    4. On the displayed page, confirm the DB instance information.

      • If you need to modify the specifications, click Previous to modify parameters.
      • If you do not need to modify the specifications, click Submit to start the instance creation.
      -

    5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

      • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
      • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
      • You can change the database port after the DB instance is created. DDS uses port 8635 by default, which is different from the default port numbers used by databases. To ensure database accessibility, you need to add the required security group rule.
      -

    -
    -
    -
    -
    -
    Parent topic: Getting Started with Clusters
    -
    -
    - diff --git a/docs/dds/umn/dds_02_0009.html b/docs/dds/umn/dds_02_0009.html index 074a8fd91..832a9c02f 100644 --- a/docs/dds/umn/dds_02_0009.html +++ b/docs/dds/umn/dds_02_0009.html @@ -1,15 +1,16 @@ -

    Connecting to a Cluster Instance

    -

    -
    +

    Connecting to a Cluster Instance Over Private Networks

    +
    diff --git a/docs/dds/umn/dds_02_0010.html b/docs/dds/umn/dds_02_0010.html index bdef47460..8111ba8ea 100644 --- a/docs/dds/umn/dds_02_0010.html +++ b/docs/dds/umn/dds_02_0010.html @@ -1,17 +1,15 @@ -

    Service Process

    -

    This section describes how to create a replica set instance, set a security group, and connect to a replica set instance.

    -

    Intended Audience

    • Users who create the DDS DB instance for the first time.
    • Users who need to perform the initial configuration after a DB instance is created.
    • Users who want to know how to connect to the DDS DB instances.
    +

    Overview

    +

    Scenarios

    This section describes how to create a cluster instance on the management console, set a security group, and connect to a cluster instance over private networks.

    -

    Service Process

    The following describes the steps from creating a DB instance to using it.

    -
    Figure 1 Accessing DB instances from a public network
    -
    Figure 2 Accessing DB instances from a private network
    +

    Process

    The following describes the steps from creating a DB instance to using it.

    +
    Figure 1 Accessing DB instances from a private network
    diff --git a/docs/dds/umn/dds_02_0011.html b/docs/dds/umn/dds_02_0011.html deleted file mode 100644 index 9a04781d3..000000000 --- a/docs/dds/umn/dds_02_0011.html +++ /dev/null @@ -1,65 +0,0 @@ - - -

    Restrictions

    -

    To improve the stability and security of DB instances, there are some restrictions on the use of DDS. For details, see Table 1.

    - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 Function restrictions

    Operation

    -

    Restrictions

    -

    Connecting to a DB instance through a client

    -
    • To access a DDS DB instance which is not publicly accessible from an ECS, the instance must be in the same VPC subnet as the ECS.
    • By default, DDS cannot be accessed through an ECS in a different security group. You need to add an inbound rule to the DDS security group.
    • The default DDS port number is 8635. You can change it if you want to access DDS through another port.
    -

    Deployment

    -

    ECSs in which DB instances are deployed are not visible to you. Your applications can access the database only through an IP address and port.

    -

    Obtaining permissions of user rwuser

    -

    Only the rwuser user permissions are provided on the instance creation page.

    -

    For details about the related commands, see Which Commands are Supported or Restricted by DDS?

    -

    Setting database parameters

    -

    -

    -

    Most database parameters in the parameter groups you created can be modified. For details, see section Editing a Parameter Group.

    -

    -

    Migrating data

    -

    You can use command line tools, including mongoexport and mongoimport, to migrate data. For details, see section Migrating Data.

    -

    Storage engine

    -

    Currently, DDS supports the WiredTiger storage engine only.

    -

    Restarting a DB instance or a node

    -

    A DDS DB instance must be restarted on the DDS console.

    -

    Viewing DDS backup files

    -

    You can download and view the backup files on the DDS console. For details, see section Downloading Backup Files.

    -
    -
    -
    -
    -
    -
    Parent topic: Getting Started with Replica Sets
    -
    -
    - diff --git a/docs/dds/umn/dds_02_0012.html b/docs/dds/umn/dds_02_0012.html index 7921d73a8..41b93e3d6 100644 --- a/docs/dds/umn/dds_02_0012.html +++ b/docs/dds/umn/dds_02_0012.html @@ -1,62 +1,67 @@

    Creating a Replica Set Instance

    -

    Scenarios

    This section describes how to create a DDS replica set instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your business needs.

    -

    You can use your account to create a maximum of 50 replica set instances in total. To create more replica set instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

    +

    Scenarios

    This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your business needs.

    +

    You can use your account to create up to 50 replica set instances. To create more replica set instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

    -

    Procedure

    1. Log in to the DDS console.
    2. On the Instance Management page, click Create DB Instance.
    3. On the displayed page, configure parameters about DB instance specifications. Then, click Create Now.

      -

      Table 1 Basic information

      Parameter

      +

      Procedure

      1. Log in to the DDS console.
      2. On the Instance Management page, click Create DB Instance.
      3. On the displayed page, select your DB instance specifications and click Create Now.

        +

        - - - - - - - - - - - - - - - - - + + + @@ -65,130 +70,132 @@
        Table 1 Basic information

        Parameter

        Description

        +

        Description

        Region

        +

        Region

        A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

        -
        NOTE:

        DB instances 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, exercise caution when selecting a region.

        +

        A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

        +
        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 Instance Name

        +

        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 Modifying the 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 Changing a DB Instance Name.

        Database Type

        +

        Database Type

        Community Edition

        +

        Community Edition

        DB Instance Type

        +

        DB Instance Type

        Select Replica set.

        +

        Select Replica set.

        A replica set consists of the primary node, secondary node, and hidden node. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability.

        Compatible MongoDB Version

        +

        Compatible MongoDB Version

        • 3.4
        • 3.2
        +
        • 4.2
        • 4.0
        • 3.4
        • 3.2

        Storage Engine

        +

        Storage Type

        WiredTiger

        +

        Ultra-high I/O

        AZ

        +

        Storage Engine

        A physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through the internal network. For details, see section Regions and AZs.

        -

        A replica set instance can be deployed in one AZ or three AZs only. If the replica set instance is deployed across three AZs, the primary, secondary, and hidden nodes are deployed in three AZs respectively for high availability.

        +

        WiredTiger

        Disk Encryption

        +

        AZ

        • Disable: Disable the encryption function.
        • Enable: 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 a DB instance is created, the disk encryption status and the key cannot be changed. Backup data stored on 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.
          +

        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 Regions and AZs.

        +
        • Instances can be deployed in one or three AZ(s). Selecting multiple AZs distributes the nodes between them.
        +

        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 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 2 Specifications

        Parameter

        +
        - - - - - - - -
        Table 2 Specifications

        Parameter

        Description

        +

        Description

        Node Class

        +

        Node Class

        For details about the DB instance specifications, see section DB Instance Specifications. After a DB instance is created, you can change its CPU and memory. For details, see section Changing the CPU or Memory of a Replica Set DB Instance.

        +

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

        Storage Type

        +

        Storage Space

        Ultra-high I/O: uses the SSD disk type.

        -

        Storage Space

        -

        Ranges from 10 GB to 2,000 GB. The value must be a multiple of 10.

        +

        The value ranges from 10 GB to 3000 GB and must be a multiple of 10.
        -
        Table 3 Network

        Parameter

        +
        - - - - - - - - + + + - - + + +
        Table 3 Network

        Parameter

        Description

        +

        Description

        VPC

        +

        VPC

        The VPC to which a DB instance belongs isolates networks for different services. It allows user to manage and configure internal networks and change network configuration, simplifying network management. You need to create or select the required VPC. For details on how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide.

        -

        Subnet

        -

        A subnet provides dedicated network resources that are logically isolated from other networks, improving network security. After a DB instance is created, you can click the DB instance name and change the private IP address assigned by the subnet to the node on the Basic Information page.

        -
        NOTE:

        Changing the private IP address of a node will invalidate the previous private IP address. If an EIP is bound to the node, do not unbind the EIP during the change of the private IP address. After the change, the new private IP address is bound to the EIP.

        +

        The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

        +
        NOTE:

        After the DDS instance is created, the VPC cannot be changed.

        Security Group

        +

        Subnet

        A security group controls access between DDS and other services for security.

        +

        A subnet provides dedicated network resources that are logically isolated from other networks for network security.

        +

        After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

        +

        Security Group

        +

        A security group controls access between DDS and other services for security.

        NOTE:

        Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

        SSL

        +

        SSL

        Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

        -

        You can enable SSL to improve data security. After a DB instance is created, you can connect to it in SSL mode. For details, see Connecting to a DB Instance Through a Client.

        +

        Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

        +

        You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

        +

        Cross-CIDR Access

        +
        • Configure

          Add the VPC CIDR block of your client. Ensure that the ECS where your client is installed can connect to the DB instance.

          +
          NOTE:
          • To ensure the ECS and the DB instance can communicate with each other, configure a VPC peering connection by referring to section "VPC Peering Connection Overview" in the Virtual Private Cloud User Guide.
          • Up to 30 CIDR blocks can be configured, and each of them can overlap but they cannot be the same. That is, the source CIDR blocks can overlap but cannot be the same.
          +
          +
        • Skip

          Configure the subnet of the client later. After a DB instance is created, you can configure cross-CIDR access by referring to Configuring Cross-CIDR Access for Replica Set Instances.

          +
        -
        Table 4 Database configuration

        Parameter

        +
        - - - - - - - - -
        Table 4 Database configuration

        Parameter

        Description

        +

        Description

        Administrator

        +

        Administrator

        The default account is rwuser.

        +

        The default account is rwuser.

        Administrator Password

        +

        Administrator Password

        The password is a string of 8 to 32 characters. It must be a combination of uppercase letters, lowercase letters, digits, and special characters. You can also use the following special characters: ~!@#%^*-_=+?

        -

        The system cannot save you password. Keep the password secure.

        +

        Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

        +

        Keep this password secure. If lost, the system cannot retrieve it for you.

        Confirm Password

        +

        Confirm Password

        The value of this parameter must be the same as the Administrator Password.

        +

        Enter the administrator password again.

        Replica Set Parameter Group

        +

        Replica Set Parameter Template

        The parameters in the replica set parameter group are applied to replica set instances. After a DB instance is created, you can change the parameter group of the instance. For a parameter group created by users, you can modify the parameters in the parameter group to bring out the best performance.

        -

        -

        -

        For details, see Parameter Group.

        -

        +

        The parameters that apply to the replica set instances. After a DB instance is created, you can change the parameter template you configured for the DB instance to bring out the best performance.

        +

        For details, see Modifying a Parameter Template.
        -
        Table 5 Tag

        Parameter

        +
        - -
        Table 5 Tag

        Parameter

        Description

        +

        Description

        Tags

        Tags a DDS DB instance. This configuration is optional. Adding tags to DDS DB instances helps you better identify and manage them. Each DB instance can have up to 20 tags.

        +

        This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

        A tag is composed of a key-value pair.

        -
        • Key: Mandatory if the DB instance is going to be tagged
          • For each DB instance, each tag key is unique.
          • A tag key consists of a maximum of 36 characters.
          • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
          -
        • Value: Optional if the DB instance is going to be tagged
          • The value consists of a maximum of 43 characters.
          • The value can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
          +
          • Key: Mandatory if the DB instance is going to be tagged
            • Each tag key must be unique for each DB instance.
            • A tag key consists of up to 36 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          • Value: Optional if the DB instance is going to be tagged
            • The value consists of up to 43 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
          -

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag.

          +

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.
        -

        The performance of your DB instance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the class and storage space of the replica set.

        +

        DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the class and storage space of the replica set.

        -

      4. On the displayed page, confirm the DB instance information.

        • If you need to modify the specifications, click Previous to modify parameters.
        • If you do not need to modify the specifications, click Submit to start the instance creation.
        -

      5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

        • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
        • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
        • You can change the database port after the DB instance is created. DDS uses port 8635 by default, which is different from the default port numbers used by databases. To ensure database accessibility, you need to add the required security group rule.
        +

      6. On the displayed page, confirm the DB instance information.

        • If you need to modify the specifications, click Previous to return to the previous page.
        • If you do not need to modify the specifications, click Submit to start the instance creation.
        +

      7. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

        • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
        • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
        • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.

        8. diff --git a/docs/dds/umn/dds_02_0013.html b/docs/dds/umn/dds_02_0013.html index 827dc6748..ca1a640c9 100644 --- a/docs/dds/umn/dds_02_0013.html +++ b/docs/dds/umn/dds_02_0013.html @@ -1,56 +1,24 @@ -

        Setting a Security Group

        -

        Scenarios

        This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group. This document describes how to set security groups.

        -
        -

        Background Information

        You can access a DDS DB instance in either of the following ways:

        -
        • Public network
        • Internal network
        -
        -

        Precautions

        The default security group rule allows all outgoing data packets. ECSs and DDS DB instances can access each other in the same security group. After a security group is created, you can add security group rules to control the access from and to the DDS DB instances in the security group.

        -

        By default, a tenant can create a maximum of 500 security group rules. An excessive number of security group rules increases the network latency of the first packet. It is recommended that you add a maximum of 50 rules for each security group.

        -

        To access the DDS DB instances in a security group from external resources, create an inbound rule for the security group.

        -
        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and project.
        3. Click Service List. Under Network, click Virtual Private Cloud.
        4. In the navigation pane on the left, choose Access Control > Security Groups.
        5. On the Security Group page, click the security group name.
        6. On the Inbound Rules tab, click Add Rule. In the displayed Add Inbound Rule dialog box, set required parameters to add inbound rules. On the Outbound Rules tab, click Add Rule. In the displayed Add Outbound Rule dialog box, set required parameters to add outbound rules.
        7. Add a security group rule as prompted.

          -

          - - - - - - - - - - - - - - - - - -
          Table 1 Parameter description

          Parameter

          -

          Description

          -

          Value Example

          -

          Protocol

          -

          Specifies the network protocol. Allows all traffic or supports user-defined protocols, TCP, UDP, ICMP, and SSH.

          -

          TCP

          -

          Port

          -

          Specifies the port allowing the access to ECSs or external devices.

          -

          8635

          -

          Source/Destination

          -

          Specifies the supported IP address and security group.

          -
          • IP address: indicates that the security group rule takes effect in a specified IP address range.
            • xxx.xxx.xxx.xxx/32 (IPv4)
            • xxx.xxx.xxx.0/24 (subnet)
            • 0.0.0.0/0 (any IP address)
            -
          • Security group: indicates that this rule allows all IP addresses of ECSs to access DDS DB instances in the same specified security group.
          -
          • 192.168.10.0/24
          • default
          -
          -
          -

        8. Click OK.
        -
        +

        Connecting to a Cluster Instance Over Public Networks

        +

        diff --git a/docs/dds/umn/dds_02_0014.html b/docs/dds/umn/dds_02_0014.html index ff89bfbc6..0210db935 100644 --- a/docs/dds/umn/dds_02_0014.html +++ b/docs/dds/umn/dds_02_0014.html @@ -1,20 +1,15 @@ -

        Connecting to a Replica Set Instance

        -

        +

        Overview

        +

        Scenarios

        This section describes how to create a cluster instance on the management console, set a security group, bind an EIP, and connect to a cluster instance over public networks.

        +
        +

        Process

        The following describes the steps from creating a DB instance to using it.

        +
        Figure 1 Accessing DB instances from a public network
        +
        diff --git a/docs/dds/umn/dds_02_0015.html b/docs/dds/umn/dds_02_0015.html deleted file mode 100644 index 8201ed085..000000000 --- a/docs/dds/umn/dds_02_0015.html +++ /dev/null @@ -1,25 +0,0 @@ - - -

        Binding and Unbinding an EIP

        -

        Scenarios

        You can access DDS through a private IP address or an EIP. The application scenario of the connection address is as follows:

        -
        • Use a private IP address when:

          DDS provides a private IP address by default.

          -

          Your applications are deployed on an ECS in a region where your replica set instance is located.

          -
        -
        • Use an EIP when:
          • Your applications are deployed on an ECS in a region separated from the region where your replica set instance is located.
          • Your applications are deployed on another cloud platform.
          -
        -
        -

        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 replica set instance, only primary and secondary nodes 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 replica set instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Bind EIP in the Operation column.
        4. In the displayed dialog box, all EIPs in the unbound status 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.
        5. In the EIP column, check that the EIP 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 replica set instance that has been bound with an EIP.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Unbind EIP in the Operation column.
        4. In the displayed dialog box, click OK to unbind the EIP.

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

          -

        -
        -
        - - diff --git a/docs/dds/umn/dds_02_0016.html b/docs/dds/umn/dds_02_0016.html index a9165d367..77aa7e48c 100644 --- a/docs/dds/umn/dds_02_0016.html +++ b/docs/dds/umn/dds_02_0016.html @@ -1,19 +1,229 @@ -

        Enabling or Disabling SSL

        -

        Scenarios

        DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.

        -
        • If SSL is enabled, you can connect to a database using SSL. For details, see SSL Connection.
        • If SSL is disabled, you can connect to the database using a common connection. For details, see Common Connection.
        -

        Enabling or disabling SSL will cause DB instance restart. Exercise caution when you perform this operation.

        +

        Creating a Cluster Instance

        +

        Scenarios

        This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your business needs.

        +

        You can use your account to create up to 10 cluster instances. To create more cluster instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

        +
        +

        Procedure

        1. Log in to the DDS console.
        2. On the Instance Management page, click Create DB Instance.
        3. On the displayed page, select your DB instance specifications and click Create Now.

          +

          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 1 Basic information

          Parameter

          +

          Description

          +

          Region

          +

          A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

          +
          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 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 Changing a DB Instance Name.

          +

          +

          +

          Database Type

          +

          Community Edition

          +

          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.

          +

          Compatible MongoDB Version

          +
          • 4.2
          • 4.0
          • 3.4
          • 3.2
          +

          Storage Type

          +

          Ultra-high I/O

          +

          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 Regions and AZs.

          +

          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 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.
            +
            +
          +
          -

          Enabling SSL

          1. On the Instance Management page, click the target replica set instance.
          2. In the navigation pane on the left, choose Connections.
          3. In the Basic Information area, click next to the SSL field.
          4. In the displayed dialog box, click Yes.
          5. In the Basic Information area, view the modification result.
          + +
          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 2 Specifications

          Parameter

          +

          Description

          +

          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.

          +

          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.

          +

          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.

          +

          For details, see Modifying a Parameter Template.

          +

          shard node class

          +

          For details about the shard 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.

          +

          shard storage space

          +

          The value ranges from 10 GB to 2000 GB and must be a multiple of 10. After a DB instance is created, you can scale up its storage space. For details, see section Scaling Up Storage Space.

          +

          shard nodes

          +

          The number of shard nodes. The shard node stores user data but cannot be accessed directly.

          +

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

          +

          shard parameter template

          +

          The parameters that apply to the shard 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.

          +

          config node class

          +

          The CPU and memory of a config node. The config node stores the DB instance configurations but cannot be accessed directly. For details, see DB Instance Specifications.

          +

          config storage space

          +

          The storage space is 20 GB and cannot be scaled up.

          +

          config parameter template

          +

          The parameters that apply to the config 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.

          +
          -

          Disabling SSL

          1. On the Instance Management page, click the target replica set instance.
          2. In the navigation pane on the left, choose Connections.
          3. In the Basic Information area, click next to the SSL field.
          4. In the displayed dialog box, click Yes.
          5. In the Basic Information area, view the modification result.
          + +
          + + + + + + + + + + + + + + + + +
          Table 3 Network

          Parameter

          +

          Description

          +

          VPC

          +

          The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. You need to create or select the required VPC. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

          +
          NOTE:

          After the DDS instance is created, the VPC cannot be changed.

          +
          +

          Subnet

          +

          A subnet provides dedicated network resources that are logically isolated from other networks for network security.

          +

          After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

          +

          Security Group

          +

          A security group controls access between DDS and other services for security.

          +
          NOTE:

          Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

          +
          +

          SSL

          +

          Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

          +

          You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

          +
          +
          + +
          + + + + + + + + + + + + + +
          Table 4 Database configuration

          Parameter

          +

          Description

          +

          Administrator

          +

          The default account is rwuser.

          +

          Administrator Password

          +

          Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

          +

          Keep this password secure. If lost, the system cannot retrieve it for you.

          +

          Confirm Password

          +

          Enter the administrator password again.

          +
          +
          + +
          + + + + + + + +
          Table 5 Tag

          Parameter

          +

          Description

          +

          Tags

          +

          This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

          +

          A tag is composed of a key-value pair.

          +
          • Key: Mandatory if the DB instance is going to be tagged
            • Each tag key must be unique for each DB instance.
            • A tag key consists of up to 36 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          • Value: Optional if the DB instance is going to be tagged
            • The value consists of up to 43 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          +

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.

          +
          +
          +

          DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the node class and storage space.

          +
          +

        4. On the displayed page, confirm the DB instance information.

          • If you need to modify the specifications, click Previous to return to the previous page.
          • If you do not need to modify the specifications, click Submit to start the instance creation.
          +

        5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

          • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
          • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
          • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.
          +

        diff --git a/docs/dds/umn/dds_02_0019.html b/docs/dds/umn/dds_02_0019.html new file mode 100644 index 000000000..072c50467 --- /dev/null +++ b/docs/dds/umn/dds_02_0019.html @@ -0,0 +1,18 @@ + + +

        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.

        +
        +

        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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0022.html b/docs/dds/umn/dds_02_0022.html new file mode 100644 index 000000000..f2af50351 --- /dev/null +++ b/docs/dds/umn/dds_02_0022.html @@ -0,0 +1,18 @@ + + +

        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.

        +
        +

        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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0023.html b/docs/dds/umn/dds_02_0023.html new file mode 100644 index 000000000..fd6785bfb --- /dev/null +++ b/docs/dds/umn/dds_02_0023.html @@ -0,0 +1,194 @@ + + +

        Creating a Single Node Instance

        +

        Scenarios

        This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your business needs.

        +

        You can use your account to create a maximum of 20 single nodes in total. To create more single node instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

        +
        +

        Procedure

        1. Log in to the DDS console.
        2. On the Instance Management page, click Create DB Instance.
        3. On the displayed page, select your DB instance specifications and click Create Now.

          +

          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 1 Basic information

          Parameter

          +

          Description

          +

          Region

          +

          A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

          +
          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 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 Changing a DB Instance Name.

          +

          +

          +

          Database Type

          +

          Community Edition

          +

          DB Instance Type

          +

          Select Single Node.

          +

          The single node architecture is another option for you, helping you reduce costs while ensuring data reliability.

          +

          Compatible MongoDB Version

          +
          • 4.2
          • 4.0
          • 3.4
          • 3.2
          +

          Storage Type

          +

          Ultra-high I/O

          +

          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 Regions and AZs.

          +

          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 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 2 Specifications

          Parameter

          +

          Description

          +

          Node Class

          +

          For details about the DB instance specifications, see section DB Instance Specifications.

          +

          Storage Space

          +

          The value ranges from 10 GB to 1,000 GB and must be a multiple of 10.

          +
          +
          + +
          + + + + + + + + + + + + + + + + +
          Table 3 Network

          Parameter

          +

          Description

          +

          VPC

          +

          The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. You need to create or select the required VPC. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

          +

          If there are no VPCs available, DDS allocates resources to you by default.

          +
          NOTE:

          After the DDS instance is created, the VPC cannot be changed.

          +
          +

          Subnet

          +

          A subnet provides dedicated network resources that are logically isolated from other networks for network security.

          +

          After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

          +

          Security Group

          +

          A security group controls access between DDS and other services for security.

          +
          NOTE:

          Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

          +
          +

          SSL

          +

          Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

          +

          You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

          +
          +
          + +
          + + + + + + + + + + + + + + + + +
          Table 4 Database configuration

          Parameter

          +

          Description

          +

          Administrator

          +

          The default account is rwuser.

          +

          Administrator Password

          +

          Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

          +

          Keep this password secure. If lost, the system cannot retrieve it for you.

          +

          Confirm Password

          +

          Enter the administrator password again.

          +

          Single Node Parameter Template

          +

          The parameters that apply to single node instances. After a DB instance is created, you can change the parameter template you configured for the DB instance to bring out the best performance.

          +

          +

          +

          For details, see Modifying a Parameter Template.

          +
          +
          + +
          + + + + + + + +
          Table 5 Tag

          Parameter

          +

          Description

          +

          Tags

          +

          This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

          +

          A tag is composed of a key-value pair.

          +
          • Key: Mandatory if the DB instance is going to be tagged
            • Each tag key must be unique for each DB instance.
            • A tag key consists of up to 36 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          • Value: Optional if the DB instance is going to be tagged
            • The value consists of up to 43 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          +

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.

          +
          +
          +

          DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the node class and storage space.

          +
          +

        4. On the displayed page, confirm the DB instance information.

          • If you need to modify the specifications, click Previous to return to the previous page.
          • If you do not need to modify the specifications, click Submit to start the instance creation.
          +

        5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

          • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
          • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
          • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0024.html b/docs/dds/umn/dds_02_0024.html new file mode 100644 index 000000000..f1db1b064 --- /dev/null +++ b/docs/dds/umn/dds_02_0024.html @@ -0,0 +1,18 @@ + + +

        Setting a Security Group

        +

        Scenarios

        This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.

        +
        +

        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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0026.html b/docs/dds/umn/dds_02_0026.html new file mode 100644 index 000000000..3294358be --- /dev/null +++ b/docs/dds/umn/dds_02_0026.html @@ -0,0 +1,22 @@ + + +

        Binding an EIP

        +

        Scenarios

        After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, 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.
        • 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 single node instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Bind EIP in the Operation column.

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

          +

        4. 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.
        5. Locate the target node, in the EIP column, 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 single node instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Unbind EIP in the Operation column.

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

          +

        4. 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_0028.html b/docs/dds/umn/dds_02_0028.html new file mode 100644 index 000000000..4bdc1ff91 --- /dev/null +++ b/docs/dds/umn/dds_02_0028.html @@ -0,0 +1,60 @@ + + +

        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.

        +

        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.

        + +
        +

        Constraints

        For details about constraints on connecting to a single node instance, see Constraints and Recommendations.

        +
        +

        Prerequisites

        1. For details on how to create and log in to an ECS, 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.
        2. Install the MongoDB client on the ECS.

          For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

          +
        +
        +

        Connecting to a DB Instance Using the MongoDB Client (SSL)

        If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

        +
        +
        1. On the Instance Management page, click the target DB instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, click next to the SSL field.

          The certificate can also be downloaded from the Node Information area on the Basic Information page.

          +
          +

        4. Upload the root certificate to the ECS to be connected to the DB instance.

          The following describes how to upload the certificate to a Linux and Window ECS:

          +
          • In Linux, run the following command:
            scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
            • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
            • REMOTE_USER indicates the ECS OS user.
            • REMOTE_ADDRESS indicates the ECS address.
            • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
            +
            +
            +
          +
          • In Windows, upload the root certificate using the remote connection tool.
          +

        5. Connect to a DDS DB instance.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

            mongo mongodb://rwuser:<password>@<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 single node instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection over private networks.
          • 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.
          +
          +
          • Connect to the DB instance using standard parameters. The following is an example command:

            mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          • Connect to the DB instance using standard URI format. The following is an example command:

            mongo mongodb://rwuser:<password>@192.168.1.6:8635/test?authSource=admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          +

        6. Check the connection result. If the following information is displayed, the connection is successful.

          replica:PRIMARY>
          +

        +
        +

        Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

        If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

        +
        +
        1. Connect to a DDS DB instance.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

            mongo mongodb://rwuser:<password>@<DB_HOST>:<DB_PORT>/test?authSource=admin

            +

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

            +
          +
          • 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.
          +
          +
          • Connect to the DB instance using standard parameters. The following is an example command:

            mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

            +
          • Connect to the DB instance using standard URI format. The following is an example command:

            mongo mongodb://rwuser:<password>@192.168.1.6:8635/test?authSource=admin

            +
          +

        2. Check the connection result. If the following information is displayed, the connection is successful.

          replica:PRIMARY>
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0042.html b/docs/dds/umn/dds_02_0042.html new file mode 100644 index 000000000..1db18ae4c --- /dev/null +++ b/docs/dds/umn/dds_02_0042.html @@ -0,0 +1,46 @@ + + +

        Connection Methods

        +

        You can access DDS over private or public networks.

        + +
        + + + + + + + + + + + + + + + + +
        Table 1 Connection methods

        Method

        +

        IP Address

        +

        Scenario

        +

        Description

        +

        Private network

        +

        Private IP address

        +

        DDS provides a private IP address by default.

        +
        • You are advised to use private IP address in following scenarios:
          • Your ECS instance is in the same VPC subnet as the DDS DB instance
          • ECS subnet and DDS subnet are connected to each other by VPC peering.
          +
        +
        • By default, DDS is not accessible from ECSs that are not in the same security group. If the ECS is not in the same group, you need to add an inbound rule to enable access.
        • The default DDS port is 8635, but this port can be modified if necessary.
        +

        Secure and excellent performance

        +

        Public network

        +

        EIP

        +
        • If your applications are running on an ECS that is in a different region from the one where the DB instance is located, you are advised to use an EIP to connect the ECS to your DDS DB instances.
        • If your applications are deployed on another cloud platform, EIP is recommended.
        +
        • Low security
        • For faster transmission and improved security, you are advised to migrate your applications to an ECS that is in the same subnet as your DDS instance and use a private IP address to access the instance.
        +
        +
        +
        +
        +
        +
        Parent topic: Getting Started with Replica Sets
        +
        +
        + diff --git a/docs/dds/umn/dds_02_0043.html b/docs/dds/umn/dds_02_0043.html index 9d94b4a32..d8772995e 100644 --- a/docs/dds/umn/dds_02_0043.html +++ b/docs/dds/umn/dds_02_0043.html @@ -1,10 +1,10 @@ -

        Logging In to the DDS Console

        +

        Logging in to the DDS Console

        Prerequisites

        You have registered an account.

        -

        For the first time you use DDS, register an account at the official website. After the registration, your account has permissions to access the DDS service, as well as all other cloud services.

        +

        For the first time you use DDS, apply for an account at the official website. After the application is successful, your account has permissions to access the DDS service, as well as all other cloud services.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
        +

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
        diff --git a/docs/dds/umn/dds_02_0046.html b/docs/dds/umn/dds_02_0046.html new file mode 100644 index 000000000..a08cadc1d --- /dev/null +++ b/docs/dds/umn/dds_02_0046.html @@ -0,0 +1,22 @@ + + +

        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.
        +
        +

        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.

          +

        +
        +

        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.

          +

        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 new file mode 100644 index 000000000..65c5acf97 --- /dev/null +++ b/docs/dds/umn/dds_02_0047.html @@ -0,0 +1,87 @@ + + +

        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.

        +

        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.

        +
        +

        Prerequisites

        1. Bind an EIP to the Replica set instance and set security group rules to ensure that the EIP can be accessed with the DB client application.
        2. Install the MongoDB client or Robo 3T.

          MongoDB client

          +
          1. For details on how to create and log in to an ECS, 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.
          2. Install the MongoDB client on the ECS.

            For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

            +
          +

          Robo 3T

          +

          For details on how to install Robo 3T, see How Do I Install Robo 3T?

          +
        3. If SSL is enabled, download the SSL certificate on the DDS console.
          1. On the Instance Management page, click the target DB instance.
          2. In the navigation pane on the left, choose Connections.
          3. In the Basic Information area, click next to the SSL field.
          +

          The certificate can also be downloaded from the Node Information area on the Basic Information page.

          +
          +
        +
        +

        Connecting to a DB Instance Using Robo 3T (SSL)

        If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

        +
        +
        1. Run the installed Robo 3T. On the displayed dialog box, click Create.

          Figure 1 Connections
          +

        2. In the Connection Settings dialog box, set the parameters of the new connection.

          1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the replica set instance in the Address text box.
            Figure 2 Connection
            +
          2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the replica set instance.
            Figure 3 Authentication
            +
          3. On the SSL tab, upload the SSL certificate and select Allowed for Invalid Hostnames.
            Figure 4 SSL
            +
          4. Click Save.
          +

        3. On the MongoDB Connections page, click Connect to connect to the replica set instance.

          Figure 5 Connections
          +

        4. If the replica set instance is successfully connected, the page shown in Figure 6 is displayed.

          Figure 6 Connection succeeded
          +

        +
        +

        Connecting to a DB Instance Using Robo 3T (Non-SSL)

        If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

        +
        +
        1. Run the installed Robo 3T. On the displayed dialog box, click Create.

          Figure 7 Connections
          +

        2. In the Connection Settings dialog box, set the parameters of the new connection.

          1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the replica set instance in the Address text box.
            Figure 8 Connection
            +
          2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the replica set instance.
            Figure 9 Authentication
            +
          3. Click Save.
          +

        3. On the MongoDB Connections page, click Connect to connect to the replica set instance.

          Figure 10 Connections
          +

        4. If the replica set instance is successfully connected, the page shown in Figure 11 is displayed.

          Figure 11 Connection succeeded
          +

        +
        +

        Connecting to a DB Instance Using the MongoDB Client (SSL)

        If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

        +
        +
        1. On the Instance Management page, click the target DB instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, click next to the SSL field.
        4. Upload the root certificate to the ECS to be connected to the DB instance.

          The following describes how to upload the certificate to a Linux and Window ECS:

          +
          • In Linux, run the following command:
            scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
            • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
            • REMOTE_USER indicates the ECS OS user.
            • REMOTE_ADDRESS indicates the ECS address.
            • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
            +
            +
            +
          • In Windows, upload the root certificate using the remote connection tool.
          +

        5. Connect to the DB instance in the directory where the MongoDB client is located.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

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

            +

            To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

            +
          +
          • A replica set instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection through a public network.
          • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
          +
          +
          • Connect to the instance using standard parameters. The following is an example command:

            mongo --host replica/192.168.1.6,192.168.1.80 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          • Connect to the DB instance Using standard URI format. The following is an example command:

            mongo "mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin&replicaSet=replica" --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          +

        6. Check the connection result. If the following information is displayed, the connection is successful.

          • Result from connecting to the primary node in a replica set or connecting to the whole replica set:
            replica:PRIMARY>
            +
          • Result from connecting the secondary node in a replica set:
            replica:SECONDARY>
            +
          +

        +
        +

        Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

        If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

        +
        +
        1. Connect to a DDS DB instance.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

            mongo "mongodb://rwuser:<password>@<DB_HOST>:<DB_PORT>/test?authSource=admin&replicaSet=replica"

            +

            To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

            +
          +
          • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
          +
          +
          • Connect to the instance using standard parameters. The following is an example command:

            mongo --host replica/192.168.1.6,192.168.1.80 --port 8635 -u rwuser -p --authenticationDatabase admin

            +
          • Connect to the DB instance Using standard URI format. The following is an example command:

            mongo "mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin&replicaSet=replica"

            +
          +

        2. Check the connection result. If the following information is displayed, the connection is successful.

          • Result from connecting to the primary node in a replica set or connecting to the whole replica set:
            replica:PRIMARY>
            +
          • Result from connecting the secondary node in a replica set:
            replica:SECONDARY>
            +
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0048.html b/docs/dds/umn/dds_02_0048.html new file mode 100644 index 000000000..72a6171fa --- /dev/null +++ b/docs/dds/umn/dds_02_0048.html @@ -0,0 +1,84 @@ + + +

        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.

        +

        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.

        + +
        +

        Prerequisites

        1. Bind an EIP to the Single node instance and set security group rules to ensure that the EIP can be accessed with the DB client application.
        2. Install the MongoDB client or Robo 3T.

          MongoDB client

          +
          1. For details on how to create and log in to an ECS, 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.
          2. Install the MongoDB client on the ECS.

            For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

            +
          +

          Robo 3T

          +

          For details on how to install Robo 3T, see How Do I Install Robo 3T?

          +
        3. If SSL is enabled, download the SSL certificate on the DDS console.
          1. On the Instance Management page, click the target DB instance.
          2. In the navigation pane on the left, choose Connections.
          3. In the Basic Information area, click next to the SSL field.
          +

          The certificate can also be downloaded from the Node Information area on the Basic Information page.

          +
          +
        +
        +

        Connecting to a DB Instance Using Robo 3T (SSL)

        If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

        +
        +
        1. Run the installed Robo 3T. On the displayed dialog box, click Create.

          Figure 1 Connections
          +

        2. In the Connection Settings dialog box, set the parameters of the new connection.

          1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the single-node instance in the Address text box.
            Figure 2 Connection
            +
          2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the single-node instance.
            Figure 3 Authentication
            +
          3. On the SSL tab, upload the SSL certificate and select Allowed for Invalid Hostnames.
            Figure 4 SSL
            +
          4. Click Save.
          +

        3. On the MongoDB Connections page, click Connect to connect to the single-node instance.

          Figure 5 Connections
          +

        4. If the single-node instance is successfully connected, the page shown in Figure 6 is displayed.

          Figure 6 Connection succeeded
          +

        +
        +

        Connecting to a DB Instance Using Robo 3T (Non-SSL)

        If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

        +
        +
        1. Run the installed Robo 3T. On the displayed dialog box, click Create.

          Figure 7 Connections
          +

        2. In the Connection Settings dialog box, set the parameters of the new connection.

          1. On the Connection tab, enter the name of the new connection in the Name text box and enter the EIP and database port that are bound to the single-node instance in the Address text box.
            Figure 8 Connection
            +
          2. On the Authentication tab, set Database to admin, User Name to rwuser, and Password to the administrator password you set during the creation of the single-node instance.
            Figure 9 Authentication
            +
          3. Click Save.
          +

        3. On the MongoDB Connections page, click Connect to connect to the single-node instance.

          Figure 10 Connections
          +

        4. If the single-node instance is successfully connected, the page shown in Figure 11 is displayed.

          Figure 11 Connection succeeded
          +

        +
        +

        Connecting to a DB Instance Using the MongoDB Client (SSL)

        If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

        +
        +
        1. On the Instance Management page, click the target DB instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, click next to the SSL field.
        4. Upload the root certificate to the ECS to be connected to the DB instance.

          The following describes how to upload the certificate to a Linux and Window ECS:

          +
          • In Linux, run the following command:
            scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
            • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
            • REMOTE_USER indicates the ECS OS user.
            • REMOTE_ADDRESS indicates the ECS address.
            • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
            +
            +
            +
          +
          • In Windows, upload the root certificate using the remote connection tool.
          +

        5. Connect to the DB instance in the directory where the MongoDB client is located.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

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

            +

            To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

            +
          +
          • A single node instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection through a public network.
          • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
          +
          +
          • Connect to the instance using standard parameters. The following is an example command:

            mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          • Connect to the DB instance using standard URI format. The following is an example command:

            mongo mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

            +
          +

        6. Check the connection result. If the following information is displayed, the connection is successful.

          replica:PRIMARY>
          +

        +
        +

        Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

        If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

        +
        +
        1. Connect to a DDS DB instance.

          • Method 1: Using standard parameters

            mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

            +

            Enter the database account password when prompted:

            +
            Enter password:
            +
          • Method 2: Using standard URI format

            mongo mongodb://rwuser:<password>@<DB_HOST>:<DB_PORT>/test?authSource=admin

            +

            To obtain the public connection address, click the instance name and choose Connections. The address is displayed in Public Network Connection Address field on the Public Connection tab.

            +
          +
          • DB_HOST indicates the IP address of the remotely connected DB instance. Obtain the value from the EIP 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.
          +
          +
          • Connect to the instance using standard parameters. The following is an example command:

            mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

            +
          • Connect to the DB instance using standard URI format. The following is an example command:

            mongo mongodb://rwuser:<password>@192.168.1.80:8635/test?authSource=admin

            +
          +

        2. Check the connection result. If the following information is displayed, the connection is successful.

          replica:PRIMARY>
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0049.html b/docs/dds/umn/dds_02_0049.html new file mode 100644 index 000000000..70d5ef5ce --- /dev/null +++ b/docs/dds/umn/dds_02_0049.html @@ -0,0 +1,18 @@ + + +

        Setting a Security Group

        +

        Scenarios

        This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how to set security groups.

        +
        +

        Precautions

        The default security group rule allows all outgoing data packets. By default, 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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0050.html b/docs/dds/umn/dds_02_0050.html new file mode 100644 index 000000000..b1077b135 --- /dev/null +++ b/docs/dds/umn/dds_02_0050.html @@ -0,0 +1,24 @@ + + +

        Connecting to a Replica Set Instance Over Public Networks

        +

        +
        + + diff --git a/docs/dds/umn/dds_02_0051.html b/docs/dds/umn/dds_02_0051.html new file mode 100644 index 000000000..143c8485c --- /dev/null +++ b/docs/dds/umn/dds_02_0051.html @@ -0,0 +1,15 @@ + + +

        Overview

        +

        Scenarios

        This section describes how to create a replica set instance on the management console, set a security group, bind an EIP, and connect to a replica set instance over public networks.

        +
        +

        Process

        The following describes the steps from creating a DB instance to using it.

        +
        Figure 1 Accessing DB instances from a public network
        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0052.html b/docs/dds/umn/dds_02_0052.html new file mode 100644 index 000000000..c9f35063b --- /dev/null +++ b/docs/dds/umn/dds_02_0052.html @@ -0,0 +1,201 @@ + + +

        Creating a Replica Set Instance

        +

        Scenarios

        This section describes how to create a replica set instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your business needs.

        +

        You can use your account to create up to 50 replica set instances. To create more replica set instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

        +
        +

        Procedure

        1. Log in to the DDS console.
        2. On the Instance Management page, click Create DB Instance.
        3. On the displayed page, select your DB instance specifications and click Create Now.

          +

          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 1 Basic information

          Parameter

          +

          Description

          +

          Region

          +

          A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

          +
          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 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 Changing a DB Instance Name.

          +

          +

          +

          Database Type

          +

          Community Edition

          +

          DB Instance Type

          +

          Select Replica set.

          +

          A replica set consists of the primary node, secondary node, and hidden node. If a primary node goes down or becomes faulty, a secondary node is automatically assigned to the primary role and continues normal operation. If a secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability.

          +

          Compatible MongoDB Version

          +
          • 4.2
          • 4.0
          • 3.4
          • 3.2
          +

          Storage Type

          +

          Ultra-high I/O

          +

          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 Regions and AZs.

          +
          • Instances can be deployed in one or three AZ(s). Selecting multiple AZs distributes the nodes between them.
          +

          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 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 2 Specifications

          Parameter

          +

          Description

          +

          Node Class

          +

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

          +

          Storage Space

          +

          The value ranges from 10 GB to 3000 GB and must be a multiple of 10.

          +
          +
          + +
          + + + + + + + + + + + + + + + + + + + +
          Table 3 Network

          Parameter

          +

          Description

          +

          VPC

          +

          The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

          +
          NOTE:

          After the DDS instance is created, the VPC cannot be changed.

          +
          +

          Subnet

          +

          A subnet provides dedicated network resources that are logically isolated from other networks for network security.

          +

          After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

          +

          Security Group

          +

          A security group controls access between DDS and other services for security.

          +
          NOTE:

          Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

          +
          +

          SSL

          +

          Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

          +

          You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

          +

          Cross-CIDR Access

          +
          • Configure

            Add the VPC CIDR block of your client. Ensure that the ECS where your client is installed can connect to the DB instance.

            +
            NOTE:
            • To ensure the ECS and the DB instance can communicate with each other, configure a VPC peering connection by referring to section "VPC Peering Connection Overview" in the Virtual Private Cloud User Guide.
            • Up to 30 CIDR blocks can be configured, and each of them can overlap but they cannot be the same. That is, the source CIDR blocks can overlap but cannot be the same.
            +
            +
          • Skip

            Configure the subnet of the client later. After a DB instance is created, you can configure cross-CIDR access by referring to Configuring Cross-CIDR Access for Replica Set Instances.

            +
          +
          +
          + +
          + + + + + + + + + + + + + + + + +
          Table 4 Database configuration

          Parameter

          +

          Description

          +

          Administrator

          +

          The default account is rwuser.

          +

          Administrator Password

          +

          Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

          +

          Keep this password secure. If lost, the system cannot retrieve it for you.

          +

          Confirm Password

          +

          Enter the administrator password again.

          +

          Replica Set Parameter Template

          +

          The parameters that apply to the replica set instances. After a DB instance is created, you can change the parameter template you configured for the DB instance to bring out the best performance.

          +

          For details, see Modifying a Parameter Template.

          +
          +
          + +
          + + + + + + + +
          Table 5 Tag

          Parameter

          +

          Description

          +

          Tags

          +

          This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

          +

          A tag is composed of a key-value pair.

          +
          • Key: Mandatory if the DB instance is going to be tagged
            • Each tag key must be unique for each DB instance.
            • A tag key consists of up to 36 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          • Value: Optional if the DB instance is going to be tagged
            • The value consists of up to 43 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          +

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.

          +
          +
          +

          DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the class and storage space of the replica set.

          +
          +

        4. On the displayed page, confirm the DB instance information.

          • If you need to modify the specifications, click Previous to return to the previous page.
          • If you do not need to modify the specifications, click Submit to start the instance creation.
          +

        5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

          • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
          • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
          • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0053.html b/docs/dds/umn/dds_02_0053.html new file mode 100644 index 000000000..855016964 --- /dev/null +++ b/docs/dds/umn/dds_02_0053.html @@ -0,0 +1,22 @@ + + +

        Binding an EIP

        +

        Scenarios

        After you create a DB instance, you can bind it to an EIP to allow external access. If later you want to prohibit external access, 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 replica set instance, only primary and secondary nodes 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 replica set instance.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Bind EIP in the Operation column.

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

          +

        4. 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.
        5. Locate the target node, in the EIP column, 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 replica set instance that has been bound with an EIP.
        2. In the navigation pane on the left, choose Connections.
        3. In the Basic Information area, locate the target node and click Unbind EIP in the Operation column.

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

          +

        4. 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_0054.html b/docs/dds/umn/dds_02_0054.html new file mode 100644 index 000000000..1028198a0 --- /dev/null +++ b/docs/dds/umn/dds_02_0054.html @@ -0,0 +1,18 @@ + + +

        Setting a Security Group

        +

        Scenarios

        This section guides you on how to add a security group rule to control access from and to DDS DB instances associated with a security group. The following describes how to set security groups.

        +
        +

        Precautions

        The default security group rule allows all outgoing data packets. By default, 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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0055.html b/docs/dds/umn/dds_02_0055.html new file mode 100644 index 000000000..c30233117 --- /dev/null +++ b/docs/dds/umn/dds_02_0055.html @@ -0,0 +1,22 @@ + + +

        Connecting to a Replica Set Instance Over Private Networks

        +

        +
        + + diff --git a/docs/dds/umn/dds_02_0057.html b/docs/dds/umn/dds_02_0057.html new file mode 100644 index 000000000..904d80e5b --- /dev/null +++ b/docs/dds/umn/dds_02_0057.html @@ -0,0 +1,15 @@ + + +

        Overview

        +

        Scenarios

        This section describes how to create a replica set instance on the management console, set a security group, and connect to a replica set instance over private networks.

        +
        +

        Process

        The following describes the steps from creating a DB instance to using it.

        +
        Figure 1 Accessing DB instances from a private network
        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0070.html b/docs/dds/umn/dds_02_0070.html new file mode 100644 index 000000000..4366f9b4c --- /dev/null +++ b/docs/dds/umn/dds_02_0070.html @@ -0,0 +1,45 @@ + + +

        Connection Methods

        +

        You can access DDS over private or public networks.

        + +
        + + + + + + + + + + + + + + + + +
        Table 1 Connection methods

        Method

        +

        IP Address

        +

        Scenario

        +

        Description

        +

        Private network

        +

        Private IP address

        +

        DDS provides a private IP address by default.

        +
        • You are advised to use private IP address in following scenarios:
          • Your ECS instance is in the same VPC subnet as the DDS DB instance
          • ECS subnet and DDS subnet are connected to each other by VPC peering.
          +
        • By default, DDS is not accessible from ECSs that are not in the same security group. If the ECS is not in the same group, you need to add an inbound rule to enable access.
        • The default DDS port is 8635, but this port can be modified if necessary.
        +

        Secure and excellent performance

        +

        Public network

        +

        EIP

        +
        • If your applications are running on an ECS that is in a different region from the one where the DB instance is located, you are advised to use an EIP to connect the ECS to your DDS DB instances.
        • If your applications are deployed on another cloud platform, EIP is recommended.
        +
        • Low security
        • For faster transmission and improved security, you are advised to migrate your applications to an ECS that is in the same subnet as your DDS instance and use a private IP address to access the instance.
        +
        +
        +
        +
        +
        +
        Parent topic: Getting Started with Single Nodes
        +
        +
        + diff --git a/docs/dds/umn/dds_02_0074.html b/docs/dds/umn/dds_02_0074.html new file mode 100644 index 000000000..c6b3258d2 --- /dev/null +++ b/docs/dds/umn/dds_02_0074.html @@ -0,0 +1,22 @@ + + +

        Connecting to a Single-Node Instance Over Private Networks

        +

        +
        + + diff --git a/docs/dds/umn/dds_02_0075.html b/docs/dds/umn/dds_02_0075.html new file mode 100644 index 000000000..259a8d58d --- /dev/null +++ b/docs/dds/umn/dds_02_0075.html @@ -0,0 +1,15 @@ + + +

        Overview

        +

        Scenarios

        This section describes how to create a single node instance on the management console, set a security group, and connect to a single node instance over private networks.

        +
        +

        Process

        The following describes the steps from creating a DB instance to using it.

        +
        Figure 1 Accessing DB instances from a private network
        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0077.html b/docs/dds/umn/dds_02_0077.html new file mode 100644 index 000000000..690900cfa --- /dev/null +++ b/docs/dds/umn/dds_02_0077.html @@ -0,0 +1,24 @@ + + +

        Connecting to a Single Node Instance Over Public Networks

        +

        +
        + + diff --git a/docs/dds/umn/dds_02_0078.html b/docs/dds/umn/dds_02_0078.html new file mode 100644 index 000000000..5b7126483 --- /dev/null +++ b/docs/dds/umn/dds_02_0078.html @@ -0,0 +1,15 @@ + + +

        Overview

        +

        Scenarios

        This section describes how to create a single node instance on the management console, set a security group, bind an EIP, and connect to a single node instance over public networks.

        +
        +

        Process

        The following describes the steps from creating a DB instance to using it.

        +
        Figure 1 Accessing DB instances from a public network
        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0079.html b/docs/dds/umn/dds_02_0079.html new file mode 100644 index 000000000..ce2f6c7cf --- /dev/null +++ b/docs/dds/umn/dds_02_0079.html @@ -0,0 +1,194 @@ + + +

        Creating a Single Node Instance

        +

        Scenarios

        This section describes how to create a single node instance on the DDS management console. DDS allows you to tailor your computing resources and storage space to your business needs.

        +

        You can use your account to create a maximum of 20 single nodes in total. To create more single node instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

        +
        +

        Procedure

        1. Log in to the DDS console.
        2. On the Instance Management page, click Create DB Instance.
        3. On the displayed page, select your DB instance specifications and click Create Now.

          +

          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Table 1 Basic information

          Parameter

          +

          Description

          +

          Region

          +

          A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

          +
          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 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 Changing a DB Instance Name.

          +

          +

          +

          Database Type

          +

          Community Edition

          +

          DB Instance Type

          +

          Select Single Node.

          +

          The single node architecture is another option for you, helping you reduce costs while ensuring data reliability.

          +

          Compatible MongoDB Version

          +
          • 4.2
          • 4.0
          • 3.4
          • 3.2
          +

          Storage Type

          +

          Ultra-high I/O

          +

          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 Regions and AZs.

          +

          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 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 2 Specifications

          Parameter

          +

          Description

          +

          Node Class

          +

          For details about the DB instance specifications, see section DB Instance Specifications.

          +

          Storage Space

          +

          The value ranges from 10 GB to 1,000 GB and must be a multiple of 10.

          +
          +
          + +
          + + + + + + + + + + + + + + + + +
          Table 3 Network

          Parameter

          +

          Description

          +

          VPC

          +

          The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. You need to create or select the required VPC. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

          +

          If there are no VPCs available, DDS allocates resources to you by default.

          +
          NOTE:

          After the DDS instance is created, the VPC cannot be changed.

          +
          +

          Subnet

          +

          A subnet provides dedicated network resources that are logically isolated from other networks for network security.

          +

          After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

          +

          Security Group

          +

          A security group controls access between DDS and other services for security.

          +
          NOTE:

          Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

          +
          +

          SSL

          +

          Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

          +

          You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

          +
          +
          + +
          + + + + + + + + + + + + + + + + +
          Table 4 Database configuration

          Parameter

          +

          Description

          +

          Administrator

          +

          The default account is rwuser.

          +

          Administrator Password

          +

          Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

          +

          Keep this password secure. If lost, the system cannot retrieve it for you.

          +

          Confirm Password

          +

          Enter the administrator password again.

          +

          Single Node Parameter Template

          +

          The parameters that apply to single node instances. After a DB instance is created, you can change the parameter template you configured for the DB instance to bring out the best performance.

          +

          +

          +

          For details, see Modifying a Parameter Template.

          +
          +
          + +
          + + + + + + + +
          Table 5 Tag

          Parameter

          +

          Description

          +

          Tags

          +

          This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

          +

          A tag is composed of a key-value pair.

          +
          • Key: Mandatory if the DB instance is going to be tagged
            • Each tag key must be unique for each DB instance.
            • A tag key consists of up to 36 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          • Value: Optional if the DB instance is going to be tagged
            • The value consists of up to 43 characters.
            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
            +
          +

          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.

          +
          +
          +

          DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the node class and storage space.

          +
          +

        4. On the displayed page, confirm the DB instance information.

          • If you need to modify the specifications, click Previous to return to the previous page.
          • If you do not need to modify the specifications, click Submit to start the instance creation.
          +

        5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

          • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
          • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
          • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.
          +

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0080.html b/docs/dds/umn/dds_02_0080.html new file mode 100644 index 000000000..20ab6ce4f --- /dev/null +++ b/docs/dds/umn/dds_02_0080.html @@ -0,0 +1,18 @@ + + +

        Setting a Security Group

        +

        Scenarios

        This section guides you on how to add a security group rule to control access from and to DDS DB instances in a security group.

        +
        +

        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.

        +

        For details about the constraints on using security groups, see "Security Group Overview" in the Virtual Private Cloud User Guide.

        +
        +

        Procedure

        For details about setting a security group, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.

        +
        +
        + + diff --git a/docs/dds/umn/dds_02_0100.html b/docs/dds/umn/dds_02_0100.html new file mode 100644 index 000000000..d07981273 --- /dev/null +++ b/docs/dds/umn/dds_02_0100.html @@ -0,0 +1,38 @@ + + +

        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.

        +

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

        +
        +

        Before You Start

        +
        • DDS supports cluster instances of Community Edition 3.2, 3.4, 4.0, and 4.2.
        • DDS creates two connection addresses for the primary node and secondary node in a shard respectively.
        • Once the connection addresses are assigned to your nodes, they cannot be modified or deleted.
        • The connection address is accessible from private networks only.
        +
        +

        Enabling shard IP Address

        1. Log in to the DDS console.
        2. In the left navigation pane, choose Instance Management. In the DB instance list, click the target cluster instance to go to the Basic Information page.

          Alternatively, on the Basic Information page, in the navigation pane on the left, click Connections.

          +

        3. In the Node Information area, click the shard tab.
        4. Click Show shard IP Address. In the displayed dialog box, enter and confirm the password for connecting to the node.

          • After the shard IP address is enabled, you need to restart the corresponding shard nodes for the configuration to take effect.
          • The shard IP address cannot be modified or disabled after being enabled, and the password cannot be modified.
          • After the shard IP address is enabled and new shard nodes are added, you need to manually locate the newly added shard node and choose More > Show shard IP Address in the Operation column to show the shard IP address.
          • After the shard IP address is enabled, all shard nodes in the current instance apply for connection addresses.
          +
          +

        5. Obtain the private IP address of the shard node.

          After the shard IP address is enabled, you can click Connections in the navigation pane on the left or on the current page to expand the node drop-down list and obtain the private IP address.

          +

        6. Obtain the connection address of a shard node.

          Example:

          +

          Based on the private IP address obtained in 5, the connection address of the current shard node is as follows:

          +

          mongodb://sharduser:<password>@192.168.237.15:8637,192.168.255.217:8637/test?authSource=admin&replicaSet=shard_?

          +
          • sharduser is the default user when setting up "show shard IP address" function.
          • <password>indicates the password of the sharduser.
          • 192.168.237.15 and 192.168.255.217 are the private IP addresses of the shard's primary and secondary nodes.
          • 8637 is the port of the shard node and cannot be changed.
          • shard_? indicates the name of the shard node to be connected, for example, shard_1.
          +
          +

        +
        +

        Enabling config IP Address

        1. Log in to the DDS console.
        2. In the left navigation pane, choose Instance Management. In the DB instance list, click the target cluster instance to go to the Basic Information page.

          Alternatively, on the Basic Information page, in the navigation pane on the left, click Connections.

          +

        3. In the Node Information area, click the config tab.
        4. Click Show config IP Address. In the displayed dialog box, enter and confirm the password for connecting to the node.

          • After the config IP address is enabled, you need to restart the corresponding config node for the configuration to take effect.
          • The config IP address cannot be modified or disabled after being enabled, and the password cannot be modified.
          +
          +

        5. Obtain the private IP address of the config node.

          After the config IP address is enabled, you can click Connections in the navigation pane on the left or on the current page to expand the node drop-down list and obtain the private IP address.

          +

        6. Obtain the connection address of a config node.

          Example:

          +

          Based on the private IP address obtained in 5, the connection address of the current config node is as follows:

          +

          mongodb://csuser:<password>@192.168.154.71:8636,192.168.143.227:8636/test?authSource=admin&replicaSet=config

          +
          • csuser indicates the username of the current config node.
          • <password>indicates the password of the csuser.
          • 192.168.154.71 and 192.168.143.227 are the private IP addresses of the current node.
          • 8636 is the port of the config node and cannot be changed.
          +
          +

        +
        +
        +
        +
        +
        Parent topic: Connection Management
        +
        +
        + diff --git a/docs/dds/umn/dds_02_cluster.html b/docs/dds/umn/dds_02_cluster.html index 5c4fa8f39..f4bb07c3d 100644 --- a/docs/dds/umn/dds_02_cluster.html +++ b/docs/dds/umn/dds_02_cluster.html @@ -4,15 +4,11 @@
        diff --git a/docs/dds/umn/dds_02_replica_set.html b/docs/dds/umn/dds_02_replica_set.html index 634d27038..5ca52e199 100644 --- a/docs/dds/umn/dds_02_replica_set.html +++ b/docs/dds/umn/dds_02_replica_set.html @@ -4,15 +4,11 @@
        diff --git a/docs/dds/umn/dds_02_single_node.html b/docs/dds/umn/dds_02_single_node.html new file mode 100644 index 000000000..a316ee7f8 --- /dev/null +++ b/docs/dds/umn/dds_02_single_node.html @@ -0,0 +1,16 @@ + + +

        Getting Started with Single Nodes

        +

        +
        + + diff --git a/docs/dds/umn/dds_03_0001.html b/docs/dds/umn/dds_03_0001.html index 44116b629..f315e584a 100644 --- a/docs/dds/umn/dds_03_0001.html +++ b/docs/dds/umn/dds_03_0001.html @@ -1,28 +1,12 @@ -

        Managing DDS DB Instances

        +

        Account Management

        diff --git a/docs/dds/umn/dds_03_0002.html b/docs/dds/umn/dds_03_0002.html index 5482be597..394cadbdd 100644 --- a/docs/dds/umn/dds_03_0002.html +++ b/docs/dds/umn/dds_03_0002.html @@ -1,24 +1,30 @@ -

        DB Instance Operations

        +

        Instance Management

        diff --git a/docs/dds/umn/dds_03_0003.html b/docs/dds/umn/dds_03_0003.html index 6af37cc68..1eff219c5 100644 --- a/docs/dds/umn/dds_03_0003.html +++ b/docs/dds/umn/dds_03_0003.html @@ -1,22 +1,22 @@

        Restarting a DB Instance or a Node

        -

        Scenarios

        You may need to restart a DB instance for maintenance purposes. After modifying some parameters, you must restart the DB instance for the modifications to take effect on the management console.

        +

        Scenarios

        You may need to occasionally restart a DB instance to perform routine maintenance. For example, after modifying certain parameters, you must restart the DB instance for the modifications to take effect on the management console.

        You can restart a DB instance only when its status is Available.

        -
        • After you restart a DB instance, services will be interrupted. Exercise caution when performing this operation.
        • If you restart a DB instance, all nodes in the instance will be restarted.
        +
        • Restarting a DB instance interrupts services, so you should exercise caution when performing this operation.
        • If you restart a DB instance, all nodes in the instance are also restarted.
        -

        Restarting a DB Instance

        1. Log in to the DDS console.
        2. On the Instance Management page, locate the target DB instance and choose More > Restart in the Operation column.

          Alternatively, click the target DB instance. On the displayed Basic Information page, click Restart in the upper right corner of the page.

          +

          Restarting a DB Instance

          1. Log in to the DDS console.
          2. On the Instance Management page, locate the target DB instance and in the Operation column, choose More > Restart.

            Alternatively, click the target DB instance and on the displayed Basic Information page, click Restart in the upper right corner of the page.

          3. In the displayed dialog box, click Yes.
          4. 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 mongos, shard, or config, locate the target node, and 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 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.

          -
          Parent topic: DB Instance Operations
          +
          Parent topic: Instance Management
          diff --git a/docs/dds/umn/dds_03_0004.html b/docs/dds/umn/dds_03_0004.html index cee5cbbb3..7703aea49 100644 --- a/docs/dds/umn/dds_03_0004.html +++ b/docs/dds/umn/dds_03_0004.html @@ -1,17 +1,18 @@ -

          Deleting a DB instance

          +

          Deleting a DB Instance

          Scenarios

          This section guides you on how to delete a DB instance no longer used to release resources. You can delete the following types of DB instances:

          -
          • Cluster instance
          • Replica set instance
          +
          • Cluster instance
          • Replica set instance
          • Single node instance
          -
          • After you delete an instance, all nodes in the instance are also deleted.
          • After you delete the DB instance, all data in it and all automated backups are automatically deleted and cannot be restored. Exercise caution when performing this operation.
          • By default, all manual backups are retained in DDS. You can use a backup to restore a deleted instance.
          +

          • DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are completed.

            +
          • After you delete an instance, all nodes in the instance are also deleted.
          • After you delete the DB instance, all data in it and all automated backups are automatically deleted and cannot be restored. Exercise caution when performing this operation.
          • By default, all manual backups are retained in DDS. You can use a backup to restore a deleted instance.

          Procedure

          1. Log in to the DDS console.
          2. On the Instance Management page, locate the target DB instance and choose More > Delete in the Operation column.
          3. In the displayed dialog box, click Yes.
          -
          Parent topic: DB Instance Operations
          +
          Parent topic: Instance Management
          diff --git a/docs/dds/umn/dds_03_0006.html b/docs/dds/umn/dds_03_0006.html index 45c9d891f..9574669d3 100644 --- a/docs/dds/umn/dds_03_0006.html +++ b/docs/dds/umn/dds_03_0006.html @@ -12,6 +12,10 @@
        3. Restoring a Replica Set Instance from a Backup
          4. +
        4. Restoring Replica Set Instance to a Point in Time
          +
          5. +
        5. Restoring a Single Node Instance from a Backup
          +
        6. Downloading Backup Files
        7. Deleting a Manual Backup
          @@ -19,9 +23,5 @@
        8. Deleting an Automated Backup
          9. - -
          -
          Parent topic: Managing DDS DB Instances
          -
        diff --git a/docs/dds/umn/dds_03_0007.html b/docs/dds/umn/dds_03_0007.html index b9134de7e..da9c84162 100644 --- a/docs/dds/umn/dds_03_0007.html +++ b/docs/dds/umn/dds_03_0007.html @@ -1,20 +1,20 @@

        Creating a Manual Backup

        -

        Scenarios

        This section guides you on how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.

        +

        Scenarios

        This section describes how to create a manual backup. Creating a backup for a DB instance helps ensure data can be restored if needed, ensuring data reliability.

        When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

        -

        Method 1

        1. Log in to the DDS console.
        2. On the Instance Management page, locate an available DB instance and click Create Backup or choose More > Create Backup.
        3. In the displayed dialog box, specify Backup Name and Description and click OK.

          • The manual backup 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 (_).
          • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
          -

        4. Check the result:

          • During the creation of a manual backup, you can query the backup status on the Backup Management or the Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
          • If the manual backup is successfully created, the backup status is Complete. The manual backup type is Manual and the backup method is Physical.
          +

          Method 1

          1. Log in to the DDS console.
          2. On the Instance Management page, locate an available DB instance and click Create Backup or choose More > Create Backup.
          3. In the displayed dialog box, specify Backup Name and Description (optional) and click OK.

            • The manual backup 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 (_).
            • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
            +

          4. Check the result:

            • During the creation of a manual backup, you can check the backup status on the Backup Management or an instance's Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
            • If the manual backup is successfully created, the backup status is Completed. The manual backup type is Manual.

          -

          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, click Create Backup.
          4. In the displayed dialog box, specify DB Instance Type, DB Instance Name, Backup Name and Description and click OK.

            • Only DB instances in Available status can be manually backed up.
            • The manual backup 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 (_).
            • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
            -

          5. Check the result:

            • During the creation of a manual backup, you can query the backup status on the Backup Management or the Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
            • If the manual backup is successfully created, the backup status is Complete. The manual backup type is Manual and the backup method is Physical.
            +

            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, click Create Backup.
            4. In the displayed dialog box, specify DB Instance Type, DB Instance Name, Backup Name and Description (optional) and click OK.

              • Only DB instances in Available status can be manually backed up.
              • The manual backup 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 (_).
              • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
              +

            5. Check the result:

              • During the creation of a manual backup, you can check the backup status on the Backup Management or an instance's Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
              • If the manual backup is successfully created, the backup status is Completed. The manual backup type is Manual.

            -

            Method 3

            1. Log in to the DDS console.
            2. On the Instance Management page, click an available DB instance.
            3. In the navigation pane on the left, click Backups & Restorations.
            4. On the Backups & Restorations page, click Create Backup.
            5. In the displayed dialog box, specify Backup Name and Description and click OK.

              • The manual backup 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 (_).
              • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
              -

            6. Check the result:

              • During the creation of a manual backup, you can query the backup status on the Backup Management or the Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
              • If the manual backup is successfully created, the backup status is Complete. The manual backup type is Manual and the backup method is Physical.
              +

              Method 3

              1. Log in to the DDS console.
              2. On the Instance Management page, click an available DB instance.
              3. In the navigation pane on the left, click Backups & Restorations.
              4. On the Backups & Restorations page, click Create Backup.
              5. In the displayed dialog box, specify Backup Name and Description (optional) and click OK.

                • The manual backup 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 (_).
                • The description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                +

              6. Check the result:

                • During the creation of a manual backup, you can check the backup status on the Backup Management or an instance's Backups & Restorations page. The backup status is Backing up. The time it takes to complete the backup depends on the size of the job.
                • If the manual backup is successfully created, the backup status is Completed. The manual backup type is Manual.

            diff --git a/docs/dds/umn/dds_03_0008.html b/docs/dds/umn/dds_03_0008.html index 91ccca691..41f0cd7e8 100644 --- a/docs/dds/umn/dds_03_0008.html +++ b/docs/dds/umn/dds_03_0008.html @@ -8,7 +8,7 @@

            Method 1

            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 Backups & Restorations.
            4. On the Backups & Restorations page, locate the manual backup to be deleted and click Delete.

              Backups being used to recover instances cannot be deleted.

            5. In the displayed dialog box, click Yes.
            -

            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, click the Clusters or Replica Sets tab, locate the manual backup you want to delete and click Delete in the Operation column.

              Backups being used to recover instances cannot be deleted.

              +

              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, click the Clusters, Replica Sets, or Single Nodes tab, locate the manual backup to be deleted, and click Delete in the Operation column.

                Backups being used to recover instances cannot be deleted.

              4. In the displayed dialog box, click Yes.
            diff --git a/docs/dds/umn/dds_03_0009.html b/docs/dds/umn/dds_03_0009.html index 6a04ce73c..edec27128 100644 --- a/docs/dds/umn/dds_03_0009.html +++ b/docs/dds/umn/dds_03_0009.html @@ -1,7 +1,7 @@

            Deleting an Automated Backup

            -

            Scenarios

            This section guides you on how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release storage space.

            +

            Scenarios

            This section describes how to delete an automated backup. If the automated backup policy is disabled, DDS allows you to delete stored automated backups to release storage space.

            If the automated backup policy is enabled, DDS will delete automated backups as they expire. You cannot delete them manually.

            The deletion operation is irreversible. Exercise caution when performing this operation.

            @@ -9,7 +9,7 @@

            Method 1

            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 Backups & Restorations.
            4. On the Backups & Restorations tab, locate the automated backup to be deleted and click Delete.

              Backups being used to recover instances cannot be deleted.

            5. In the displayed dialog box, click Yes.
            -

            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, click the Clusters or Replica Sets tab, locate the automated backup you want to delete and click Delete in the Operation column.

              Backups being used to recover instances cannot be deleted.

              +

              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, click the Clusters, Replica Sets, or Single Nodes tab, locate the automated backup to be deleted, and click Delete in the Operation column.

                Backups being used to recover instances cannot be deleted.

              4. In the displayed dialog box, click Yes.
            diff --git a/docs/dds/umn/dds_03_0010.html b/docs/dds/umn/dds_03_0010.html index 145581da9..bde15ab87 100644 --- a/docs/dds/umn/dds_03_0010.html +++ b/docs/dds/umn/dds_03_0010.html @@ -1,29 +1,31 @@ -

            Parameter Group

            -
            +

            Parameter Template Management

            +
            diff --git a/docs/dds/umn/dds_03_0012.html b/docs/dds/umn/dds_03_0012.html index 189315aa6..4a0594e2e 100644 --- a/docs/dds/umn/dds_03_0012.html +++ b/docs/dds/umn/dds_03_0012.html @@ -1,15 +1,14 @@ -

            Comparing Two Parameter Groups

            -

            Scenarios

            This section guides you on how to compare two parameter groups of the same node type and DB engine version to know their current settings.

            -
            -

            Procedure

            1. Log in to the DDS console.
            2. In the navigation pane on the left, click Parameter Group Management.
            3. On the Parameter Group Management page, select the Clusters or Replica Sets tab and locate the parameter group you created and click Compare in the Operation column.
            4. In the displayed Compare Parameter Group dialog box, select a parameter group for Group2 and click OK.

              If the settings of the two parameter groups are different, the parameter names and values of group 1 and group 2 parameter groups are displayed. If the settings are the same, no data is displayed.

              +

              Comparing Parameter Templates

              +

              This section describes how to compare two parameter templates of the same node type and DB engine version.

              +

              Procedure

              1. Log in to the management console.
              2. Click in the upper left corner and select a region and a project.
              3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
              4. In the navigation pane on the left, click Parameter Template Management.
              5. On the Parameter Template Management page, select the Clusters, Replica Sets, or Single Nodes tab and locate the parameter templates you created and click Compare in the Operation column.
              6. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                • If their settings are different, the parameter names and values of both parameter templates are displayed.
                • If their settings are the same, no data is displayed.

              -
              Parent topic: Parameter Group
              +
              Parent topic: Parameter Template Management
              diff --git a/docs/dds/umn/dds_03_0013.html b/docs/dds/umn/dds_03_0013.html index 93b4407f7..89bddd658 100644 --- a/docs/dds/umn/dds_03_0013.html +++ b/docs/dds/umn/dds_03_0013.html @@ -1,15 +1,16 @@ -

              Replicating a Parameter Group

              -

              Scenarios

              This section guides you on how to replicate a parameter group you created and assign it a name different from that of original group.

              -
              -

              Procedure

              1. Log in to the DDS console.
              2. In the navigation pane on the left, click Parameter Group Management.
              3. On the Parameter Group Management page, select the Clusters or Replica Sets tab, locate the parameter group you want to replicate and click Replicate in the Operation column.
              4. Enter the new parameter group name and description and click OK.

                • Parameter Group Name: specifies the parameter group name, which is a string of 1 to 64 characters composed of only letters (case-sensitive), digits, hyphens (-), underscores (_), and periods (.).
                • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                -

              5. After the creation is complete, you can manage the parameter group in the parameter group list on the corresponding tab.
              +

              Replicating a Parameter Template

              +

              You can replicate a parameter template you have created.

              +

              Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones.

              +

              Procedure

              1. Log in to the management console.
              2. Click in the upper left corner and select a region and a project.
              3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
              4. In the navigation pane on the left, click Parameter Template Management.
              5. On the Parameter Template Management page, select the Clusters, Replica Sets, or Single Nodes tab, locate the parameter template you want to replicate and click Replicate in the Operation column.
              6. In the displayed dialog box, enter the parameter template name and description and click OK.

                • New Parameter Template: The template name can be 4 to 64 characters long and starts with a letter. It can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
                • Description: The description contains a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
                +

                After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

                +

              -
              Parent topic: Parameter Group
              +
              Parent topic: Parameter Template Management
              diff --git a/docs/dds/umn/dds_03_0014.html b/docs/dds/umn/dds_03_0014.html index f08569bb4..d7ab34f37 100644 --- a/docs/dds/umn/dds_03_0014.html +++ b/docs/dds/umn/dds_03_0014.html @@ -1,19 +1,16 @@ -

              Changing Associated Parameter Group

              -

              Scenarios

              After a DB instance is created, you can change the parameter group associated with the DB instance to achieve optimal performance. The parameter group associated with the DB instance cannot be changed in any of the following cases:

              -
              • A DB instance is being restarted.
              • A backup file is being created.
              • Cluster instance nodes are being added.
              • The storage space is being expanded.
              • The instance class is being changed.
              • An SSL connection is being enabled or disabled.
              • The port is being changed.
              -
              -

              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 mongos, shard, or config, locate the target node, and click Change Parameter Group.
              4. On the displayed dialog box, select the parameter group to be modified and click OK.

                • If the static parameter value is changed in the new parameter group, restart the instance for the modification to take effect.
                • If no parameter groups are available for New Parameter Group, create a parameter group. For details, see section Creating a Parameter Group.
                -

              -
              -

              Replica Set

              1. Log in to the DDS console.
              2. On the Instance Management page, locate the target replica set instance, and choose More > Change Parameter Group in the Operation column.
              3. On the displayed dialog box, select the parameter group to be modified and click OK.

                • If the static parameter value is changed in the new parameter group, restart the instance for the modification to take effect.
                • If no parameter groups are available for New Parameter Group, create a parameter group. For details, see section Creating a Parameter Group.
                +

                Applying a Parameter Template

                +

                Modifications to parameters in a custom parameter template take effect for DB instances only after you have applied the template to the target DB instances or target nodes.

                +

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select a region and a project.
                3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                4. In the navigation pane on the left, click Parameter Template Management.
                5. On the Parameter Template Management page, apply a default template or a custom template to the target DB instance:

                  • To apply a default template, click the Default Templates tab, locate the required parameter template, and click Apply in the Operation column.
                  • To apply a custom template, click Custom Templates, locate the target parameter template, and in the Operation column, choose More > Apply.
                  +

                  A parameter template can be applied to one or more nodes and instances.

                  +

                6. In the displayed dialog box, select the node or instance to which the parameter template will be applied and click OK.

                -
                Parent topic: Parameter Group
                +
                Parent topic: Parameter Template Management
                diff --git a/docs/dds/umn/dds_03_0015.html b/docs/dds/umn/dds_03_0015.html index a5837cf31..38114751d 100644 --- a/docs/dds/umn/dds_03_0015.html +++ b/docs/dds/umn/dds_03_0015.html @@ -1,16 +1,15 @@ -

                Resetting a Parameter Group

                -

                Scenarios

                This section guides you on how to reset all parameters in a parameter group you create to the default settings as needed.

                -

                Resetting the parameter group will restore the default values. Exercise caution when performing this operation.

                -
                +

                Resetting a Parameter Template

                +

                This section describes how to reset all parameters in a parameter template you create to the default settings as needed.

                +

                Precautions

                Resetting a parameter template will restore all parameters in the parameter template to their default values. Exercise caution when performing this operation.

                -

                Procedure

                1. Log in to the DDS console.
                2. In the navigation pane on the left, click Parameter Group Management.
                3. On the Parameter Group Management page, select the Clusters or Replica Sets tab, locate the parameter group you want to reset and choose More > Reset in the Operation column.
                4. In the displayed dialog box, click Yes.
                +

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select a region and a project.
                3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                4. In the navigation pane on the left, click Parameter Template Management.
                5. On the Parameter Template Management page, select the Clusters, Replica Sets, or Single Nodes tab, locate the parameter template you want to reset and choose More > Reset in the Operation column.
                6. In the displayed dialog box, click Yes.
                -
                Parent topic: Parameter Group
                +
                Parent topic: Parameter Template Management
                diff --git a/docs/dds/umn/dds_03_0016.html b/docs/dds/umn/dds_03_0016.html index e26cfe288..25fc097d0 100644 --- a/docs/dds/umn/dds_03_0016.html +++ b/docs/dds/umn/dds_03_0016.html @@ -1,17 +1,15 @@ -

                Deleting a Parameter Group

                -

                Scenarios

                This section guides you on how to delete a parameter group. The following parameter groups cannot be deleted.

                -
                • Default parameter groups
                • Parameter groups associated with DB instances
                -

                Deleted parameter groups cannot be restored. Exercise caution when performing this operation.

                -
                +

                Deleting a Parameter Template

                +

                You can delete a custom parameter template that is no longer used.

                +

                Precautions

                • Default parameter templates and parameter templates applied to instances cannot be deleted.
                • Deleted parameter templates cannot be restored. Exercise caution when performing this operation.
                -

                Procedure

                1. Log in to the DDS console.
                2. In the navigation pane on the left, click Parameter Group Management.
                3. On the Parameter Group Management page, select the Clusters or Replica Sets tab, locate the parameter group you want to delete and choose More > Delete in the Operation column.
                4. In the displayed dialog box, click Yes.
                +

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select a region and a project.
                3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                4. In the navigation pane on the left, click Parameter Template Management.
                5. On the Parameter Template Management page, select the Clusters, Replica Sets, or Single Nodes tab, locate the parameter template you want to delete and choose More > Delete in the Operation column.
                6. In the displayed dialog box, click Yes.
                -
                Parent topic: Parameter Group
                +
                Parent topic: Parameter Template Management
                diff --git a/docs/dds/umn/dds_03_0017.html b/docs/dds/umn/dds_03_0017.html deleted file mode 100644 index 925db26c4..000000000 --- a/docs/dds/umn/dds_03_0017.html +++ /dev/null @@ -1,20 +0,0 @@ - - -

                Storage

                -

                -
                - - diff --git a/docs/dds/umn/dds_03_0018.html b/docs/dds/umn/dds_03_0018.html index 9f7ca3a1c..e78fa131f 100644 --- a/docs/dds/umn/dds_03_0018.html +++ b/docs/dds/umn/dds_03_0018.html @@ -1,18 +1,18 @@ -

                Reverting Cluster Instance Nodes

                -

                Scenarios

                This section guides you on how to revert nodes that fail to be added.

                +

                Reverting and Deleting Failed Cluster Instance Nodes

                +

                Scenarios

                This section describes how to revert nodes that fail to be added.

                -

                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 node status is Deleting node. This process takes about 1 to 3 minutes.

                  +

                  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 a Single Node

                  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 fail 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 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.

                  -
                  Parent topic: Storage
                  +
                  Parent topic: Instance Management
                  diff --git a/docs/dds/umn/dds_03_0019.html b/docs/dds/umn/dds_03_0019.html index 707c32d9e..88ded318f 100644 --- a/docs/dds/umn/dds_03_0019.html +++ b/docs/dds/umn/dds_03_0019.html @@ -1,20 +1,21 @@ -

                  Security

                  -

                  -
                  +

                  Connection Management

                  +
                  diff --git a/docs/dds/umn/dds_03_0023.html b/docs/dds/umn/dds_03_0023.html index 4de44f229..9f722aa08 100644 --- a/docs/dds/umn/dds_03_0023.html +++ b/docs/dds/umn/dds_03_0023.html @@ -1,9 +1,9 @@ -

                  Tag

                  -

                  Scenarios

                  Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally and other cloud services manage their own tags.

                  -

                  Adding tags to DDS DB instances helps you better identify and manage them. A DB instance can be tagged during or after it is created.

                  -
                  • You are advised to set predefined tags on the TMS console.
                  • A tag consists of a key and value. You can add only one value for each key. For details about the naming rules of tag keys and tag values, see Table 1.
                  • Each DB instance can have up to 20 tags.
                  +

                  Tag Management

                  +

                  Scenarios

                  Tag Management Service (TMS) enables you to use tags on the management console to manage resources. Every cloud service is responsible for managing their own tags while TMS is responsible for the global tag management.

                  +

                  Adding tags to DDS DB instances helps you better identify and manage them. A DB instance can be tagged during or after it is created.

                  +
                  • You are advised to set predefined tags on the TMS console.
                  • A tag consists of a key and value. You can add only one value for each key. For details about the naming rules of tag keys and tag values, see Table 1.
                  • Up to 20 tags can be added for a DB instance.
                  @@ -15,14 +15,14 @@ - - @@ -31,7 +31,7 @@
                  Table 1 Naming rules

                  Parameter

                  Tag key

                  • Cannot be left blank.
                  • For each DB instance, each tag key is unique.
                  • Consists of a maximum of 36 characters.
                  • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
                  +
                  • The key cannot be left blank.
                  • Each tag key must be unique for each DB instance.
                  • A tag key consists of up to 36 characters.
                  • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).

                  Organization

                  Tag value

                  • Can be empty.
                  • Consists of a maximum of 43 characters.
                  • The value can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
                  +
                  • The value consists of up to 43 characters.
                  • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).

                  dds_01

                  -

                  Adding a Tag

                  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 Tags.
                  4. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value, and click OK.
                  5. View and manage tags on the Tags page.
                  +

                  Adding a Tag

                  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 Tags.
                  4. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and value (optional), and click OK.
                  5. View and manage tags on the Tags page.

                  Editing a Tag

                  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 Tags.
                  4. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                    Only the tag value can be edited when editing a tag.

                  5. View and manage tags on the Tags page.
                  @@ -39,9 +39,4 @@

                  Deleting a Tag

                  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 Tags.
                  4. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                  5. After a tag has been deleted, it will not be displayed on the Tags page.
                  -
                  -
                  -
                  Parent topic: Managing DDS DB Instances
                  -
                  -
                  diff --git a/docs/dds/umn/dds_03_0024.html b/docs/dds/umn/dds_03_0024.html index 44a216e3b..b03866a5d 100644 --- a/docs/dds/umn/dds_03_0024.html +++ b/docs/dds/umn/dds_03_0024.html @@ -1,13 +1,10 @@ -

                  Monitoring

                  -
                  +

                  Log Management

                  +

                  +
                    -
                  • Interconnected with Cloud Eye
                    -
                    • -
                  • Interconnecting with CTS
                    -
                  • Error Log
                  • Slow Query Log
                    diff --git a/docs/dds/umn/dds_03_0025.html b/docs/dds/umn/dds_03_0025.html index 845ebdc84..e45762182 100644 --- a/docs/dds/umn/dds_03_0025.html +++ b/docs/dds/umn/dds_03_0025.html @@ -1,20 +1,16 @@ -

                    Interconnected with Cloud Eye

                    +

                    Monitoring and Alarm Reporting

                    diff --git a/docs/dds/umn/dds_03_0026.html b/docs/dds/umn/dds_03_0026.html index df6046b50..ac4093186 100644 --- a/docs/dds/umn/dds_03_0026.html +++ b/docs/dds/umn/dds_03_0026.html @@ -1,605 +1,931 @@

                    DDS Metrics

                    -

                    Cluster

                    • Table 1 lists the DB instance monitoring metrics. -
                      Table 1 DB instance monitoring metrics

                      Metrics

                      +

                      Function

                      This section describes metrics reported by Document Database Service (DDS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the metrics of the monitored object and alarms generated for DDS.

                      +
                      +

                      Namespace

                      SYS.DDS

                      +
                      +

                      Monitoring Metrics

                      +
                      - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                      Metrics

                      Unit

                      +

                      Metrics Name

                      +

                      Description

                      +

                      Value Range

                      +

                      Remarks

                      +

                      Monitoring Interval (Raw Data)

                      COMMAND Statements per Second

                      +

                      mongo001_command_ps

                      Count/s

                      +

                      COMMAND Statements per Second

                      +

                      Number of COMMAND statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      DELETE Statements per Second

                      +

                      mongo002_delete_ps

                      Count/s

                      +

                      DELETE Statements per Second

                      +

                      Number of DELETE statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      INSERT Statements per Second

                      +

                      mongo003_insert_ps

                      Count/s

                      +

                      INSERT Statements per Second

                      +

                      Number of INSERT statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      QUERY Statements per Second

                      +

                      mongo004_query_ps

                      Count/s

                      +

                      QUERY Statements per Second

                      +

                      Number of QUERY statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      UPDATE Statements per Second

                      +

                      mongo005_update_ps

                      Count/s

                      +

                      UPDATE Statements per Second

                      +

                      Number of UPDATE statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      GETMORE Statements per Second

                      +

                      mongo006_getmore_ps

                      Count/s

                      +

                      GETMORE Statements per Second

                      +

                      Number of GETMORE statements executed per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

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

                      1 minute

                      Chunks of Shard 1

                      +

                      mongo007_chunk_num1

                      Count

                      +

                      Chunks of Shard 1

                      +

                      Number of chunks in shard 1

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 2

                      +

                      mongo007_chunk_num2

                      Count

                      +

                      Chunks of Shard 2

                      +

                      Number of chunks in shard 2

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 3

                      +

                      mongo007_chunk_num3

                      Count

                      +

                      Chunks of Shard 3

                      +

                      Number of chunks in shard 3

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 4

                      +

                      mongo007_chunk_num4

                      Count

                      +

                      Chunks of Shard 4

                      +

                      Number of chunks in shard 4

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 5

                      +

                      mongo007_chunk_num5

                      Count

                      +

                      Chunks of Shard 5

                      +

                      Number of chunks in shard 5

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 6

                      +

                      mongo007_chunk_num6

                      Count

                      +

                      Chunks of Shard 6

                      +

                      Number of chunks in shard 6

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 7

                      +

                      mongo007_chunk_num7

                      Count

                      +

                      Chunks of Shard 7

                      +

                      Number of chunks in shard 7

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 8

                      +

                      mongo007_chunk_num8

                      Count

                      +

                      Chunks of Shard 8

                      +

                      Number of chunks in shard 8

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 9

                      +

                      mongo007_chunk_num9

                      Count

                      +

                      Chunks of Shard 9

                      +

                      Number of chunks in shard 9

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 10

                      +

                      mongo007_chunk_num10

                      Count

                      +

                      Chunks of Shard 10

                      +

                      Number of chunks in shard 10

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 11

                      +

                      mongo007_chunk_num11

                      Count

                      +

                      Chunks of Shard 11

                      +

                      Number of chunks in shard 11

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunks of Shard 12

                      +

                      mongo007_chunk_num12

                      Count

                      +

                      Chunks of Shard 12

                      +

                      Number of chunks in shard 12

                      +

                      0–64 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Active Instance Connections

                      +

                      mongo008_connections

                      Count

                      +

                      Active Instance Connections

                      +

                      Total number of connections attempting to connect to a DDS DB instance

                      +

                      0–200 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      Chunk Migration Failures in Last 24 hrs

                      +

                      mongo009_migFail_num

                      Count

                      +

                      Chunk Migration Failures in Last 24 hrs

                      +

                      Number of chunk migration failures in the last 24 hours

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type: DDS DB instance

                      +

                      1 minute

                      +

                      mongo007_connections

                      +

                      Active Node Connections

                      +

                      Total number of connections attempting to connect to a DDS DB instance node

                      +

                      0–200 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo008_mem_resident

                      +

                      Resident Memory

                      +

                      Size of resident memory in MB

                      +

                      ≥ 0 MB

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo009_mem_virtual

                      +

                      Virtual Memory

                      +

                      Size of virtual memory in MB

                      +

                      ≥ 0 MB

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo010_regular_asserts_ps

                      +

                      Regular Asserts per Second

                      +

                      Number of regular asserts per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo011_warning_asserts_ps

                      +

                      Warning Asserts per Second

                      +

                      Number of warning asserts per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo012_msg_asserts_ps

                      +

                      Message Asserts per Second

                      +

                      Number of message asserts per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo013_user_asserts_ps

                      +

                      User Asserts per Second

                      +

                      Number of user asserts per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo014_queues_total

                      +

                      Operations Queued Waiting for a Lock

                      +

                      Number of operations queued waiting for a lock

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo015_queues_readers

                      +

                      Operations Queued Waiting for a Read Lock

                      +

                      Number of operations queued waiting for a read lock

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo016_queues_writers

                      +

                      Operations Queued Waiting for a Write Lock

                      +

                      Number of operations queued waiting for a write lock

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo017_page_faults

                      +

                      Page Faults

                      +

                      Number of page faults on the monitored nodes

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo018_porfling_num

                      +

                      Slow Queries

                      +

                      Number of slow queries on the monitored nodes

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo019_cursors_open

                      +

                      Maintained Cursors

                      +

                      Number of maintained cursors on the monitored nodes

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo020_cursors_timeOut

                      +

                      Timeout Cursors

                      +

                      Number of timed out cursors on the monitored nodes

                      +

                      ≥ 0 Counts

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo021_wt_cahe_usage

                      +

                      Bytes in WiredTiger Cache

                      +

                      Size of data in the WiredTiger cache in MB

                      +

                      ≥ 0 MB

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo022_wt_cahe_dirty

                      +

                      Tracked Dirty Bytes in WiredTiger Cache

                      +

                      Size of tracked dirty data in the WiredTiger cache in MB

                      +

                      ≥ 0 MB

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo023_wInto_wtCache

                      +

                      Bytes Written Into Cache per Second

                      +

                      Bytes written into WiredTiger cache per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo024_wFrom_wtCache

                      +

                      Bytes Written From Cache per Second

                      +

                      Bytes written from the WiredTiger cache to the disk per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: database

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo025_repl_oplog_win

                      +

                      Oplog Window

                      +

                      Available time in hour in the monitored primary node's oplog

                      +

                      ≥ 0 Hours

                      +

                      Monitored object: database

                      +

                      Monitored object type: primary node

                      +

                      1 minute

                      +

                      mongo026_oplog_size_ph

                      +

                      Oplog Growth Rate

                      +

                      Speed in MB/hour at which oplogs are generated on the monitored primary node

                      +

                      ≥ 0 MB/Hour

                      +

                      Monitored object: database

                      +

                      Monitored object type: primary node

                      +

                      1 minute

                      +

                      mongo025_repl_headroom

                      +

                      Replication Headroom

                      +

                      Time difference in seconds between the primary's oplog window and the replication lag of the secondary

                      +

                      ≥ 0 Seconds

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo026_repl_lag

                      +

                      Replication Lag

                      +

                      A delay in seconds between an operation on the primary and the application of that operation from the oplog to the secondary

                      +

                      ≥ 0 Seconds

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo027_repl_command_ps

                      +

                      Replicated COMMAND Statements per Second

                      +

                      Number of replicated COMMAND statements executed on the secondary node per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo028_repl_update_ps

                      +

                      Replicated UPDATE Statements per Second

                      +

                      Number of replicated UPDATE statements executed on the secondary node per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo029_repl_delete_ps

                      +

                      Replicated DELETE Statements per Second

                      +

                      Number of replicated DELETE statements executed on the secondary node per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo030_repl_insert_ps

                      +

                      Replicated INSERT Statements per Second

                      +

                      Number of replicated INSERT statements executed on the secondary node per second

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: database

                      +

                      Monitored object type: secondary node

                      +

                      1 minute

                      +

                      mongo031_cpu_usage

                      +

                      CPU Usage

                      +

                      CPU usage of the monitored object

                      +

                      0–1

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo032_mem_usage

                      +

                      Memory Usage

                      +

                      Memory usage of the monitored object

                      +

                      0–1

                      +

                      Monitored object: ECS

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

                      1 minute

                      +

                      mongo033_bytes_out

                      +

                      Network Output Throughput

                      +

                      Outgoing traffic in bytes per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo034_bytes_in

                      +

                      Network Input Throughput

                      +

                      Incoming traffic in bytes per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo035_disk_usage

                      +

                      Disk Utilization

                      +

                      Disk usage of the monitored object

                      +

                      0–1

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo036_iops

                      +

                      IOPS

                      +

                      Average number of I/O requests processed by the system in a specified period

                      +

                      ≥ 0 Count/s

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo037_read_throughput

                      +

                      Disk Read Throughput

                      +

                      Number of bytes read from the disk per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo038_write_throughput

                      +

                      Disk Write Throughput

                      +

                      Number of bytes written into the disk per second

                      +

                      ≥ 0 bytes/s

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo039_avg_disk_sec_per_read

                      +

                      Average Time per Disk Read

                      +

                      Average time required for each disk read in a specified period

                      +

                      ≥ 0 Seconds

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo040_avg_disk_sec_per_write

                      +

                      Average Time per Disk Write

                      +

                      Average time required for each disk write in a specified period

                      +

                      ≥ 0 Seconds

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo042_disk_total_size

                      +

                      Total Storage Space

                      +

                      Total storage space of the monitored object

                      +

                      0–1000 GB

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo043_disk_used_size

                      +

                      Used Storage Space

                      +

                      Used storage space of the monitored object

                      +

                      0–1000 GB

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • Primary node
                      • Secondary node
                      +

                      1 minute

                      +

                      mongo044_swap_usage

                      +

                      SWAP Usage

                      +

                      Swap usage, in percentage.

                      +

                      0–1

                      +

                      Monitored object: ECS

                      +

                      Monitored object type:

                      +
                      • mongos node
                      • Secondary node
                      +

                      1 minute
                      -
                    • The monitoring metrics of the primary nodes in the config's and shard's replica sets are as follows:
                      • Table 2 lists the ECS monitoring metrics.
                      • -
                        Table 2 ECS monitoring metrics

                        Metrics

                        + +

                        Dimensions

                        +
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

                        Key

                        Unit

                        +

                        Value

                        CPU Usage

                        +

                        mongodb_cluster_id

                        Percent

                        +

                        DDS DB instance ID

                        +

                        Supported the cluster, replica set, and single node instance types.

                        Memory Usage

                        +

                        mongos_instance_id

                        Percent

                        +

                        mongos node ID

                        Network Output Throughput

                        +

                        mongod_primary_instance_id

                        bytes/s

                        +

                        Primary node ID

                        +

                        Includes the primary config and shard nodes of cluster instances and the primary nodes of replica set instances.

                        Network Input Throughput

                        +

                        mongod_secondary_instance_id

                        bytes/s

                        -

                        Disk Utilization

                        -

                        Percent

                        -

                        IOPS

                        -

                        Count/s

                        -

                        Disk Read Throughput

                        -

                        bytes/s

                        -

                        Disk Write Throughput

                        -

                        bytes/s

                        -

                        Average Time per Disk Read

                        -

                        s

                        -

                        Average Time per Disk Write

                        -

                        s

                        -

                        Total Disk Size

                        -

                        GB

                        -

                        Disk Usage

                        -

                        GB

                        +

                        Secondary node ID

                        +

                        Includes the secondary config and shard nodes of cluster instances and the secondary nodes of replica set instances.
                        - -
                        • Table 3 lists database metrics. -
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Table 3 Database metrics

                          Metrics

                          -

                          Unit

                          -

                          COMMAND Statements per Second

                          -

                          Count/s

                          -

                          DELETE Statements per Second

                          -

                          Count/s

                          -

                          INSERT Statements per Second

                          -

                          Count/s

                          -

                          QUERY Statements per Second

                          -

                          Count/s

                          -

                          UPDATE Statements per Second

                          -

                          Count/s

                          -

                          GETMORE Statements per Second

                          -

                          Count/s

                          -

                          Active Connections

                          -

                          Count

                          -

                          Resident Memory

                          -

                          MB

                          -

                          Virtual Memory

                          -

                          MB

                          -

                          Regular Asserts per Second

                          -

                          Count/s

                          -

                          Warning Asserts per Second

                          -

                          Count/s

                          -

                          Message Asserts per Second

                          -

                          Count/s

                          -

                          User Asserts per Second

                          -

                          Count/s

                          -

                          Number of Operations Queued Waiting for the Lock

                          -

                          Count

                          -

                          Operations Queued Waiting for a Read Lock

                          -

                          Count

                          -

                          Operations Queued Waiting for a Write Lock

                          -

                          Count

                          -

                          Page Faults

                          -

                          Count

                          -

                          Slow Queries

                          -

                          Count

                          -

                          Maintained Cursors

                          -

                          Count

                          -

                          Timeout Cursors

                          -

                          Count

                          -

                          Bytes in WiredTiger Cache

                          -

                          MB

                          -

                          Tracked Dirty Bytes in WiredTiger Cache

                          -

                          MB

                          -

                          Bytes Written Into Cache per Second

                          -

                          bytes/s

                          -

                          Bytes Written From Cache per Second

                          -

                          bytes/s

                          -

                          Oplog Window

                          -

                          h

                          -

                          Oplog Growth Rate

                          -

                          MB/h

                          -
                          -
                          -
                        -
                      • The monitoring metrics of the secondary or hidden nodes in the config's and shard's replica sets are as follows:
                        • The ECS monitoring metrics are the same as those of the primary nodes in the config's and shard's replica sets. For details, see Table 2.
                        • Table 4 lists database metrics. -
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Table 4 Database metrics

                          Metrics

                          -

                          Unit

                          -

                          COMMAND Statements per Second

                          -

                          Count/s

                          -

                          DELETE Statements per Second

                          -

                          Count/s

                          -

                          INSERT Statements per Second

                          -

                          Count/s

                          -

                          QUERY Statements per Second

                          -

                          Count/s

                          -

                          UPDATE Statements per Second

                          -

                          Count/s

                          -

                          GETMORE Statements per Second

                          -

                          Count/s

                          -

                          Active Node Connections

                          -

                          Count

                          -

                          Resident Memory

                          -

                          MB

                          -

                          Virtual Memory

                          -

                          MB

                          -

                          Regular Asserts per Second

                          -

                          Count/s

                          -

                          Warning Asserts per Second

                          -

                          Count/s

                          -

                          Message Asserts per Second

                          -

                          Count/s

                          -

                          User Asserts per Second

                          -

                          Count/s

                          -

                          Operations Queued Waiting for a Lock

                          -

                          Count

                          -

                          Operations Queued Waiting for a Read Lock

                          -

                          Count

                          -

                          Operations Queued Waiting for a Write Lock

                          -

                          Count

                          -

                          Page Faults

                          -

                          Count

                          -

                          Slow Queries

                          -

                          Count

                          -

                          Maintained Cursors

                          -

                          Count

                          -

                          Timeout Cursors

                          -

                          Count

                          -

                          Bytes in WiredTiger Cache

                          -

                          MB

                          -

                          Tracked Dirty Bytes in WiredTiger Cache

                          -

                          MB

                          -

                          Bytes Written Into Cache per Second

                          -

                          bytes/s

                          -

                          Bytes Written From Cache per Second

                          -

                          bytes/s

                          -

                          Replication Headroom

                          -

                          s

                          -

                          Replication Lag

                          -

                          s

                          -

                          Replicated COMMAND Statements per Second

                          -

                          Count/s

                          -

                          Replicated UPDATE Statements per Second

                          -

                          Count/s

                          -

                          Replicated DELETE Statements per Second

                          -

                          Count/s

                          -

                          Replicated INSERT Statements per Second

                          -

                          Count/s

                          -
                          -
                          -
                        -
                      • mongos metrics are as follows:
                        • Table 5 lists the ECS monitoring metrics.
                        • -
                          - - - - - - - - - - - - - - - - -
                          Table 5 ECS monitoring metrics

                          Metrics

                          -

                          Unit

                          -

                          CPU Usage

                          -

                          Percent

                          -

                          Memory Usage

                          -

                          Percent

                          -

                          Network Output Throughput

                          -

                          bytes/s

                          -

                          Network Input Throughput

                          -

                          bytes/s

                          -
                          -
                          -
                        • Table 6 lists database metrics. -
                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Table 6 Database metrics

                          Metrics

                          -

                          Unit

                          -

                          COMMAND Statements per Second

                          -

                          Count/s

                          -

                          DELETE Statements per Second

                          -

                          Count/s

                          -

                          INSERT Statements per Second

                          -

                          Count/s

                          -

                          QUERY Statements per Second

                          -

                          Count/s

                          -

                          UPDATE Statements per Second

                          -

                          Count/s

                          -

                          GETMORE Statements per Second

                          -

                          Count/s

                          -

                          Active Node Connections

                          -

                          Count

                          -

                          Resident Memory

                          -

                          MB

                          -

                          Virtual Memory

                          -

                          MB

                          -

                          Regular Asserts per Second

                          -

                          Count/s

                          -

                          Warning Asserts per Second

                          -

                          Count/s

                          -

                          Message Asserts per Second

                          -

                          Count/s

                          -

                          User Asserts per Second

                          -

                          Count/s

                          -
                          -
                          -
                        -
                        • -
                        -

                        Replica Set

                        • Monitoring metrics of the primary node
                          • Table 2 lists the ECS monitoring metrics.
                          • Table 3 lists database metrics.
                          -
                        • Monitoring metrics of the secondary or hidden node
                          • Table 2 lists the ECS monitoring metrics.
                          • Table 4 lists database metrics.
                          -
                        diff --git a/docs/dds/umn/dds_03_0027.html b/docs/dds/umn/dds_03_0027.html index 51965073a..5e6a006d0 100644 --- a/docs/dds/umn/dds_03_0027.html +++ b/docs/dds/umn/dds_03_0027.html @@ -1,20 +1,18 @@

                        Setting Alarm Rules

                        -

                        Scenarios

                        You can set DDS alarm rules to customize the monitored objects and notification policies. Then, you can learn DDS running status in a timely manner.

                        -

                        The DDS alarm rules include alarm rule name, instance, metric, threshold, monitoring interval and whether to send notification. This section describes how to set DDS alarm rules.

                        +

                        Scenarios

                        • You can enable the alarm reporting function in one click. After alarms are triggered, Simple Message Notification (SMN) can send notifications to specified cloud account.
                        • You can set DDS alarm rules to customize the monitored objects and notification policies. Then, you can learn DDS running status in a timely manner.

                        For more information about DDS alarm rules, see Cloud Eye User Guide.

                        -

                        Procedure

                        1. Log in to the management console.
                        2. Under Management & Deployment, click Cloud Eye.
                        3. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                        4. On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.

                          The following operations use the modification of an existing alarm rule as an example.

                          -

                          Locate the alarm rule to be modified and choose More > Modify.

                          -

                          Click OK.

                          -

                        5. After the alarm rule is set, the system automatically notifies you when an alarm is triggered.
                        +

                        Enable Basic Alarm Reporting

                        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, choose Advanced O&M.
                        4. On the Advanced O&M page, click the Alarms tab and click next to the target alarm policy to enable alarm reporting function.
                        5. If you want to disable the alarm reporting function, click .
                        +
                        +

                        Setting Custom Alarm Rules

                        For more information about alarm rules, see Cloud Eye User Guide.

                        diff --git a/docs/dds/umn/dds_03_0028.html b/docs/dds/umn/dds_03_0028.html index 3e120dba8..cfbb6a1ff 100644 --- a/docs/dds/umn/dds_03_0028.html +++ b/docs/dds/umn/dds_03_0028.html @@ -1,18 +1,12 @@ -

                        Interconnecting with CTS

                        +

                        Auditing

                        diff --git a/docs/dds/umn/dds_03_0029.html b/docs/dds/umn/dds_03_0029.html index 0ad41e520..f78d99af3 100644 --- a/docs/dds/umn/dds_03_0029.html +++ b/docs/dds/umn/dds_03_0029.html @@ -1,13 +1,13 @@

                        Key Operations Recorded by CTS

                        -

                        With CTS, you can record operations associated with DDS for later query, audit, and backtrack operations.

                        +

                        With Cloud Trace Service (CTS), you can record operations associated with DDS for later query, audit, and backtrack operations.

                        -
                        Table 1 Key operations on DDS

                        Operation

                        +
                        - - @@ -102,44 +102,44 @@ - - - - - - - - @@ -148,14 +148,14 @@ - -
                        Table 1 Key operations on DDS

                        Operation

                        Resource

                        +

                        Resource

                        Trace Name

                        +

                        Trace Name

                        ddsSetBackupPolicy

                        Applying a parameter group

                        +

                        Applying a parameter template

                        parameterGroup

                        ddsApplyConfigurations

                        Replicating a parameter group

                        +

                        Replicating a parameter template

                        parameterGroup

                        ddsCopyConfigurations

                        Resetting a parameter group

                        +

                        Resetting a parameter template

                        parameterGroup

                        +

                        parameterGroup

                        ddsResetConfigurations

                        Creating a parameter group

                        +

                        Creating a parameter template

                        parameterGroup

                        ddsCreateConfigurations

                        Deleting a parameter group

                        +

                        Deleting a parameter template

                        parameterGroup

                        ddsDeleteConfigurations

                        Updating a parameter group

                        +

                        Updating a parameter template

                        parameterGroup

                        +

                        parameterGroup

                        ddsUpdateConfigurations

                        instance

                        ddsBindIP

                        +

                        ddsBindEIP

                        Unbinding an EIP

                        instance

                        ddsUnbindIP

                        +

                        ddsUnBindEIP

                        Adding a tag

                        @@ -210,10 +210,12 @@
                        +

                        ddsAddTag and ddsDeleteTag are respectively used to add and delete tags for all resources. ddsAddInstanceTag and ddsDeleteInstanceTag are respectively used to add and delete tags for a single instance.

                        +
                        -
                        Parent topic: Interconnecting with CTS
                        +
                        Parent topic: Auditing
                        diff --git a/docs/dds/umn/dds_03_0030.html b/docs/dds/umn/dds_03_0030.html new file mode 100644 index 000000000..05f370102 --- /dev/null +++ b/docs/dds/umn/dds_03_0030.html @@ -0,0 +1,14 @@ + + +

                        Changing a Single Node DB Instance Class

                        +

                        Procedure

                        1. Log in to the DDS console.
                        2. On the Instance Management page, locate the target single node instance and click Change Instance Class in the Operation column.

                          Alternatively, on the Instance Management page, click the name of the single node instance. In the DB Information area on the Basic Information page, click Change to the right of the Node Class field.

                          +

                        3. On the displayed page, modify required parameters and click Submit.
                        4. 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.
                          • Go to the Basic Information page of the single node you scaled up and check whether the scaling process is successful in the Configuration area.
                          +

                        +
                        +
                        +
                        +
                        +
                        Parent topic: Changing the DB Instance Class
                        +
                        +
                        + diff --git a/docs/dds/umn/dds_03_0031.html b/docs/dds/umn/dds_03_0031.html new file mode 100644 index 000000000..afa3005c7 --- /dev/null +++ b/docs/dds/umn/dds_03_0031.html @@ -0,0 +1,28 @@ + + +

                        Restoring a Single Node Instance from a Backup

                        +

                        Scenarios

                        This section describes how to restore a single node instance from a backup.

                        +
                        +

                        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 single node 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. In the displayed window, select a restoration mode 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, and storage type must be the same as those of the original and cannot be changed.
                            • 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 Single Node 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.
                            +
                            +
                          +

                        +
                        +

                        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 Single Nodes tab and click Restore in the Operation column.
                        4. In the displayed window, select a restoration mode 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, and storage type must be the same as those of the original and cannot be changed.
                            • 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 Single Node 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.
                            +
                            +
                          +

                        +
                        +
                        +
                        +
                        +
                        Parent topic: Backup and Restore
                        +
                        +
                        + diff --git a/docs/dds/umn/dds_03_0032.html b/docs/dds/umn/dds_03_0032.html deleted file mode 100644 index b04e50a98..000000000 --- a/docs/dds/umn/dds_03_0032.html +++ /dev/null @@ -1,20 +0,0 @@ - - -

                        Querying Traces

                        -

                        Scenarios

                        After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last 7 days are stored on the CTS console.

                        -

                        This section describes how to query operation records for the last 7 days on the CTS console.

                        -
                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Management & Deployment, click Cloud Trace Service.
                        4. Choose Trace List in the navigation pane on the left.
                        5. Specify the filters used for querying traces. The following four filters are available:

                          • Trace Source, Resource Type, Search By, and Operator

                            Select the filter from the drop-down list.

                            -

                            When you select Trace name for Search By, you also need to select a specific trace name.

                            -

                            When you select Resource ID for Search By, you also need to select or enter a specific resource ID.

                            -

                            When you select Resource name for Search By, you also need to select or enter a specific resource name.

                            -
                          • Operator: Select a specific operator (a user rather than tenant).
                          • Trace Status: Available options include All trace statuses, normal, warning, and incident. You can only select one of them.
                          • Start time and end time: You can specify the time period for query traces.
                          -

                        6. Click on the left of the record to be queried to extend its details.
                        7. Locate a trace and click View Trace in the Operation column.
                        -
                        -
                        -
                        -
                        -
                        Parent topic: Interconnecting with CTS
                        -
                        -
                        - diff --git a/docs/dds/umn/dds_03_0033.html b/docs/dds/umn/dds_03_0033.html new file mode 100644 index 000000000..ee46976e0 --- /dev/null +++ b/docs/dds/umn/dds_03_0033.html @@ -0,0 +1,1153 @@ + + +

                        Which Commands are Supported or Restricted by DDS?

                        +

                        The following tables list the commands supported and restricted by DDS.

                        +

                        For more information, see official MongoDB documentation.

                        +

                        Users cannot execute a system command.

                        +
                        + +
                        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                        Table 1 Commands supported and restricted by DDS

                        Type

                        +

                        Command

                        +

                        Supported

                        +

                        Description

                        +

                        Aggregates Commands

                        +

                        aggregate

                        +

                        √

                        +

                        -

                        +

                        count

                        +

                        √

                        +

                        -

                        +

                        distinct

                        +

                        √

                        +

                        -

                        +

                        group

                        +

                        √

                        +

                        -

                        +

                        mapReduce

                        +

                        √

                        +

                        This command can be used only when the security.javascriptEnabled parameter in the parameter template associated with the DB instance is set to true.

                        +

                        Geospatial Commands

                        +

                        geoNear

                        +

                        √

                        +

                        -

                        +

                        geoSearch

                        +

                        √

                        +

                        -

                        +

                        Query and Write Operation Commands

                        +

                        find

                        +

                        √

                        +

                        -

                        +

                        insert

                        +

                        √

                        +

                        -

                        +

                        update

                        +

                        √

                        +

                        -

                        +

                        delete

                        +

                        √

                        +

                        -

                        +

                        findAndModify

                        +

                        √

                        +

                        -

                        +

                        getMore

                        +

                        √

                        +

                        -

                        +

                        getLastError

                        +

                        √

                        +

                        -

                        +

                        resetError

                        +

                        √

                        +

                        -

                        +

                        getPrevError

                        +

                        √

                        +

                        -

                        +

                        parallelCollectionScan

                        +

                        √

                        +

                        -

                        +

                        Query Plan Cache Commands

                        +

                        planCacheListFilters

                        +

                        √

                        +

                        -

                        +

                        planCacheSetFilter

                        +

                        √

                        +

                        -

                        +

                        planCacheClearFilters

                        +

                        √

                        +

                        -

                        +

                        planCacheListQueryShapes

                        +

                        √

                        +

                        -

                        +

                        planCacheListPlans

                        +

                        √

                        +

                        -

                        +

                        planCacheClear

                        +

                        √

                        +

                        -

                        +

                        Authentication Commands

                        +

                        logout

                        +

                        √

                        +

                        -

                        +

                        authenticate

                        +

                        √

                        +

                        -

                        +

                        copydbgetnonce

                        +

                        √

                        +

                        -

                        +

                        getnonce

                        +

                        √

                        +

                        -

                        +

                        authSchemaUpgrade

                        +

                        x

                        +

                        System command

                        +

                        User Management Commands

                        +

                        createUser

                        +

                        √

                        +

                        -

                        +

                        updateUser

                        +

                        √

                        +

                        -

                        +

                        dropUser

                        +

                        √

                        +

                        -

                        +

                        dropAllUsersFromDatabase

                        +

                        √

                        +

                        -

                        +

                        grantRolesToUser

                        +

                        √

                        +

                        -

                        +

                        revokeRolesFromUser

                        +

                        √

                        +

                        -

                        +

                        usersInfo

                        +

                        √

                        +

                        -

                        +

                        Role Management Commands

                        +

                        invalidateUserCache

                        +

                        √

                        +

                        -

                        +

                        createRole

                        +

                        √

                        +

                        -

                        +

                        updateRole

                        +

                        √

                        +

                        -

                        +

                        dropRole

                        +

                        √

                        +

                        -

                        +

                        dropAllRolesFromDatabase

                        +

                        √

                        +

                        -

                        +

                        grantPrivilegesToRole

                        +

                        √

                        +

                        -

                        +

                        revokePrivilegesFromRole

                        +

                        √

                        +

                        -

                        +

                        grantRolesToRole

                        +

                        √

                        +

                        -

                        +

                        revokeRolesFromRole

                        +

                        √

                        +

                        -

                        +

                        rolesInfo

                        +

                        √

                        +

                        -

                        +

                        Replication Commands

                        +

                        replSetElect

                        +

                        x

                        +

                        System command

                        +

                        replSetUpdatePosition

                        +

                        x

                        +

                        System command

                        +

                        appendOplogNote

                        +

                        x

                        +

                        System command

                        +

                        replSetFreeze

                        +

                        x

                        +

                        System command

                        +

                        replSetGetStatus

                        +

                        √

                        +

                        -

                        +

                        replSetInitiate

                        +

                        x

                        +

                        System command

                        +

                        replSetMaintenance

                        +

                        x

                        +

                        System command

                        +

                        replSetReconfig

                        +

                        x

                        +

                        System command

                        +

                        replSetStepDown

                        +

                        x

                        +

                        System command

                        +

                        replSetSyncFrom

                        +

                        x

                        +

                        System command

                        +

                        replSetRequestVotes

                        +

                        x

                        +

                        System command

                        +

                        replSetDeclareElectionWinner

                        +

                        x

                        +

                        System command

                        +

                        resync

                        +

                        x

                        +

                        System command

                        +

                        applyOps

                        +

                        x

                        +

                        System command

                        +

                        isMaster

                        +

                        √

                        +

                        -

                        +

                        replSetGetConfig

                        +

                        x

                        +

                        System command

                        +

                        Sharding Commands

                        +

                        flushRouterConfig

                        +

                        x

                        +

                        High-risk commands

                        +

                        addShard

                        +

                        x

                        +

                        Unauthorized operation

                        +

                        addShardToZone

                        +

                        √

                        +

                        -

                        +

                        balancerStart

                        +

                        √

                        +

                        -

                        +

                        balancerStatus

                        +

                        √

                        +

                        -

                        +

                        balancerStop

                        +

                        √

                        +

                        -

                        +

                        removeShardFromZone

                        +

                        √

                        +

                        -

                        +

                        updateZoneKeyRange

                        +

                        √

                        +

                        -

                        +

                        cleanupOrphaned

                        +

                        x

                        +

                        High-risk commands

                        +

                        checkShardingIndex

                        +

                        x

                        +

                        System command

                        +

                        enableSharding

                        +

                        √

                        +

                        -

                        +

                        listShards

                        +

                        x

                        +

                        System command

                        +

                        removeShard

                        +

                        x

                        +

                        High-risk commands

                        +

                        getShardMap

                        +

                        x

                        +

                        System command

                        +

                        getShardVersion

                        +

                        √

                        +

                        -

                        +

                        mergeChunks

                        +

                        √

                        +

                        -

                        +

                        setShardVersion

                        +

                        x

                        +

                        System command

                        +

                        shardCollection

                        +

                        √

                        +

                        -

                        +

                        shardingState

                        +

                        x

                        +

                        System command

                        +

                        unsetSharding

                        +

                        x

                        +

                        System command

                        +

                        split

                        +

                        √

                        +

                        -

                        +

                        splitChunk

                        +

                        √

                        +

                        -

                        +

                        splitVector

                        +

                        √

                        +

                        -

                        +

                        moveChunk

                        +

                        √

                        +

                        -

                        +

                        movePrimary

                        +

                        √

                        +

                        -

                        +

                        isdbgrid

                        +

                        √

                        +

                        -

                        +

                        Administration Commands

                        +

                        setFeatureCompatibilityVersion

                        +

                        √

                        +

                        -

                        +

                        renameCollection

                        +

                        √

                        +

                        -

                        +

                        dropDatabase

                        +

                        √

                        +

                        -

                        +

                        listCollections

                        +

                        √

                        +

                        -

                        +

                        drop

                        +

                        √

                        +

                        -

                        +

                        create

                        +

                        √

                        +

                        -

                        +

                        clone

                        +

                        x

                        +

                        System command

                        +

                        cloneCollection

                        +

                        √

                        +

                        -

                        +

                        cloneCollectionAsCapped

                        +

                        √

                        +

                        -

                        +

                        convertToCapped

                        +

                        √

                        +

                        -

                        +

                        filemd5

                        +

                        √

                        +

                        -

                        +

                        createIndexes

                        +

                        √

                        +

                        -

                        +

                        listIndexes

                        +

                        √

                        +

                        -

                        +

                        dropIndexes

                        +

                        √

                        +

                        -

                        +

                        fsync

                        +

                        √

                        +

                        -

                        +

                        clean

                        +

                        x

                        +

                        System command

                        +

                        connPoolSync

                        +

                        x

                        +

                        System command

                        +

                        connectionStatus

                        +

                        √

                        +

                        -

                        +

                        compact

                        +

                        x

                        +

                        High-risk commands

                        +

                        collMod

                        +

                        √

                        +

                        -

                        +

                        reIndex

                        +

                        √

                        +

                        -

                        +

                        setParameter

                        +

                        x

                        +

                        System configuration command

                        +

                        getParameter

                        +

                        √

                        +

                        -

                        +

                        repairDatabase

                        +

                        x

                        +

                        High-risk commands

                        +

                        repairCursor

                        +

                        x

                        +

                        System command

                        +

                        touch

                        +

                        √

                        +

                        -

                        +

                        shutdown

                        +

                        x

                        +

                        High-risk commands

                        +

                        logRotate

                        +

                        x

                        +

                        High-risk commands

                        +

                        killOp

                        +

                        √

                        +

                        -

                        +

                        Diagnostic Commands

                        +

                        availableQueryOptions

                        +

                        √

                        +

                        -

                        +

                        buildInfo

                        +

                        √

                        +

                        -

                        +

                        collStats

                        +

                        √

                        +

                        -

                        +

                        connPoolStats

                        +

                        x

                        +

                        System command

                        +

                        cursorInfo

                        +

                        x

                        +

                        System command

                        +

                        dataSize

                        +

                        √

                        +

                        -

                        +

                        dbHash

                        +

                        x

                        +

                        System command

                        +

                        dbStats

                        +

                        √

                        +

                        -

                        +

                        diagLogging

                        +

                        x

                        +

                        System command

                        +

                        driverOIDTest

                        +

                        x

                        +

                        System command

                        +

                        explain

                        +

                        √

                        +

                        -

                        +

                        features

                        +

                        √

                        +

                        -

                        +

                        getCmdLineOpts

                        +

                        x

                        +

                        System command

                        +

                        getLog

                        +

                        x

                        +

                        System command

                        +

                        hostInfo

                        +

                        x

                        +

                        System command

                        +

                        isSelf

                        +

                        x

                        +

                        System command

                        +

                        listCommands

                        +

                        √

                        +

                        -

                        +

                        listDatabases

                        +

                        √

                        +

                        -

                        +

                        netstat

                        +

                        x

                        +

                        System command

                        +

                        ping

                        +

                        √

                        +

                        -

                        +

                        profile

                        +

                        √

                        +

                        -

                        +

                        serverStatus

                        +

                        √

                        +

                        -

                        +

                        shardConnPoolStats

                        +

                        x

                        +

                        System command

                        +

                        top

                        +

                        √

                        +

                        -

                        +

                        validate

                        +

                        x

                        +

                        System configuration command

                        +

                        whatsmyuri

                        +

                        √

                        +

                        -

                        +

                        Internal Commands

                        +

                        handshake

                        +

                        x

                        +

                        System command

                        +

                        _recvChunkAbort

                        +

                        x

                        +

                        System command

                        +

                        _recvChunkCommit

                        +

                        x

                        +

                        System command

                        +

                        _recvChunkStart

                        +

                        x

                        +

                        System command

                        +

                        _recvChunkStatus

                        +

                        x

                        +

                        System command

                        +

                        _replSetFresh

                        +

                        x

                        +

                        System command

                        +

                        mapreduce.shardedfinish

                        +

                        x

                        +

                        System command

                        +

                        _transferMods

                        +

                        x

                        +

                        System command

                        +

                        replSetHeartbeat

                        +

                        x

                        +

                        System command

                        +

                        replSetGetRBID

                        +

                        x

                        +

                        System command

                        +

                        _migrateClone

                        +

                        x

                        +

                        System command

                        +

                        replSetElect

                        +

                        x

                        +

                        System command

                        +

                        writeBacksQueued

                        +

                        x

                        +

                        System command

                        +

                        writebacklisten

                        +

                        x

                        +

                        System command

                        +

                        System Events Auditing Commands

                        +

                        logApplicationMessage

                        +

                        x

                        +

                        System command

                        +
                        +
                        +
                        +
                        +
                        +
                        Parent topic: Database Commands
                        +
                        +
                        + diff --git a/docs/dds/umn/dds_03_0040.html b/docs/dds/umn/dds_03_0040.html index fda06c25c..8c98c0c9a 100644 --- a/docs/dds/umn/dds_03_0040.html +++ b/docs/dds/umn/dds_03_0040.html @@ -2,18 +2,12 @@

                        Task Center

                        Scenarios

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

                        -

                        Currently, only the following tasks can be viewed:

                        -
                        • Creating a cluster instance
                        • Creating a replica set instance
                        • Scaling up the storage space for a shard node of a cluster instance
                        • Scaling up the storage space of a replica set instance
                        -

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

                        +
                        +

                        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 that fail to be executed will be retained for seven days by default.

                        -

                        Procedure

                        1. Log in to the DDS console.
                        2. In the navigation pane on the left, click Task Center.
                        3. On the Task Center page, locate the target task and click to expand its details.

                          To identify the target task, you can use the task name and DB instance name/ID or select task status or types in the drop-down list in the upper right corner.

                          -

                        4. View the execution progress and result of the task.
                        -
                        -
                        -
                        -
                        -
                        Parent topic: Managing DDS DB Instances
                        +

                        Procedure

                        1. Log in to the DDS console.
                        2. In the navigation pane on the left, choose Task Center. Then, view the task progresses and results.
                        diff --git a/docs/dds/umn/dds_03_0042.html b/docs/dds/umn/dds_03_0042.html index 89de3283a..9abe6e09b 100644 --- a/docs/dds/umn/dds_03_0042.html +++ b/docs/dds/umn/dds_03_0042.html @@ -1,14 +1,24 @@

                        Restoring a Cluster Instance from a Backup

                        -

                        Scenarios

                        This section guides you on how to restore a DB instance from a backup.

                        +

                        Scenarios

                        This section describes how to restore a cluster instance from a backup.

                        -

                        Currently, DDS only supports restoring backups to a new DB instance.

                        +

                        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.
                            +
                          • 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.
                            -

                            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 in the backup list and click Restore in the Operation column. In the displayed dialog box, click OK.
                            5. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

                              • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ, improving data reliability.
                              • 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 quantity of mongos is 2 by default and ranges from 2 to 16. 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 are the same as those of the original DB instance by default and can be modified. For details, see section Creating a Cluster Instance.
                              +

                        -

                        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 backup to restore on the Clusters tab and click Restore in the Operation column. In the displayed dialog box, click OK.
                        4. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

                          • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ, improving data reliability.
                          • 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 quantity of mongos is 2 by default and ranges from 2 to 16. 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 are the same as those of the original DB instance by default and can be modified. For details, see section Creating a Cluster Instance.
                          +

                          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.
                              +
                            • 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_0043.html b/docs/dds/umn/dds_03_0043.html index 927497319..ebe319363 100644 --- a/docs/dds/umn/dds_03_0043.html +++ b/docs/dds/umn/dds_03_0043.html @@ -1,14 +1,24 @@

                        Restoring a Replica Set Instance from a Backup

                        -

                        Scenarios

                        This section guides you on how to restore a replica set instance from a backup.

                        +

                        Scenarios

                        This section describes how to restore a replica set instance from a backup.

                        -

                        Currently, DDS only supports restoring backups to a new DB instance.

                        +

                        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 replica set 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, and storage type must be the same as those of the original and cannot be changed.
                            • 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 Replica Set 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.
                            -

                            Method 1

                            1. Log in to the DDS console.
                            2. On the Instance Management page, click the target replica set instance.
                            3. In the navigation pane on the left, click Backups & Restorations.
                            4. On the Backups & Restorations page, locate the target backup in the backup list and click Restore in the Operation column. In the displayed dialog box, click OK.
                            5. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

                              • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ, improving data reliability.
                              • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
                              • The storage space is the same as that of the original instance by default. You can only increase the storage space.
                              • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Creating a Replica Set Instance.
                              +

                        -

                        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, click the Replica Sets tab, locate the backup to restore, and click Restore in the Operation column. In the displayed dialog box, click OK.
                        4. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

                          • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ, improving data reliability.
                          • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
                          • The storage space is the same as that of the original instance by default. You can only increase the storage space.
                          • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Creating a Replica Set Instance.
                          +

                          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 Replica Sets 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 yes, go to 4.
                              • If no, you can only restore the backup to a new DB instance. Go to Create New Instance step under Step 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, and storage type must be the same as those of the original and cannot be changed.
                              • 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 Replica Set 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.
                              +
                              +

                        diff --git a/docs/dds/umn/dds_03_0044.html b/docs/dds/umn/dds_03_0044.html index 69f397b19..d1e345fc7 100644 --- a/docs/dds/umn/dds_03_0044.html +++ b/docs/dds/umn/dds_03_0044.html @@ -1,15 +1,15 @@ -

                        Changing a Parameter Group Description

                        -

                        The description of a default parameter group cannot be modified.

                        -
                        -

                        Procedure

                        1. Log in to the DDS console.
                        2. In the navigation pane on the left, click Parameter Group Management.
                        3. On the Parameter Group Management page, select the Clusters or Replica Sets tab, locate the parameter group you created and click in the Description column.
                        4. Enter new description information. The parameter group description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=

                          • If you want to submit the change, click . After the modification is successful, you can view the new description in the Description column of the parameter group list.
                          • If you want to cancel the change, click .
                          +

                          Modifying the Description of a Parameter Template

                          +

                          Precautions

                          The description of a default parameter template cannot be modified.

                          +
                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                          4. In the navigation pane on the left, click Parameter Template Management.
                          5. On the Parameter Template Management page, locate the target parameter template, and click in the Description column.
                          6. Enter new description information. The parameter template description contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=

                            • To submit the change, click . After the modification is successful, you can view the new description in the Description column of the parameter template list.
                            • To cancel the change, click .

                          -
                          Parent topic: Parameter Group
                          +
                          Parent topic: Parameter Template Management
                          diff --git a/docs/dds/umn/dds_03_0050.html b/docs/dds/umn/dds_03_0050.html index 6b70a0cef..d9c3392de 100644 --- a/docs/dds/umn/dds_03_0050.html +++ b/docs/dds/umn/dds_03_0050.html @@ -2,16 +2,16 @@

                          Manually Switching the Primary and Secondary Nodes of a Replica Set

                          Scenarios

                          A replica set consists of the primary node, secondary node, and hidden node. Primary and secondary nodes allow access from external services by providing IP addresses. Hidden nodes are only used for backing up data. When a primary node becomes faulty, the system automatically selects a new primary node to ensure high availability. In addition, DDS supports the primary/secondary switchover so you can perform switchovers in scenarios such as disaster recovery.

                          -
                          • You can perform a switchover when the DB instance status is Available, and Changing a security group.
                          • Services may be interrupted during the switchover. Ensure that your client supports reconnection.
                          • The longer the delay for primary/secondary synchronization, the more time is needed for a primary/secondary switchover. Therefore, if the primary to secondary synchronization delay exceeds 300s, the primary/secondary switchover is not allowed. For details about the delay for the primary/secondary synchronization, see What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?
                          +
                          • You can perform a switchover when the DB instance status is Available, or Changing a security group.
                          • The database connection may be interrupted during the switchover. Ensure that your client supports reconnection.
                          • The longer the delay for primary/secondary synchronization, the more time is needed for a primary/secondary switchover. Therefore, if the primary to secondary synchronization delay exceeds 300s, the primary/secondary switchover is not allowed. For details about the synchronization delay, see What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?
                          -

                          Procedure

                          1. Log in to the DDS console.
                          2. On the Instance Management page, click the target replica set instance.
                          3. In the Node Information area on the Basic Information page, click Switch.
                          4. In the displayed dialog box, click Yes.
                          5. Check the result.

                            • During the switchover process, the DB instance status changes to Switchover in progress. After the switchover is complete, the status is restored to Available.
                            • In the Node Information area, you can view the switchover result.
                            • After the switchover, the previous primary node becomes the secondary node. You need to reconnect to the primary node. For details, see Connecting to a DB Instance Through a Client.
                            +

                            Procedure

                            1. Log in to the DDS console.
                            2. On the Instance Management page, click the target replica set instance.
                            3. In the Node Information area on the Basic Information page, click Switch.
                            4. In the displayed dialog box, click Yes.
                            5. Check the result.

                          -
                          Parent topic: DB Instance Operations
                          +
                          Parent topic: Instance Management
                          diff --git a/docs/dds/umn/dds_03_0051.html b/docs/dds/umn/dds_03_0051.html index c01aa9df2..54e6cde98 100644 --- a/docs/dds/umn/dds_03_0051.html +++ b/docs/dds/umn/dds_03_0051.html @@ -1,16 +1,17 @@

                          Exporting DB Instance Information

                          -

                          Scenarios

                          This section guides you on how to export DB instance information for analysis.

                          +

                          Scenarios

                          This section describes how to export DB instance information for analysis. The following information can be exported:

                          +
                          • Database Type
                          • DB Instance Name
                          • DB Instance ID
                          • DB Instance Type
                          • DB Engine Version
                          • Billing Mode
                          • Node ID
                          • Status
                          • Node Name
                          • Node Status
                          • Created
                          • Database Port
                          • VPC
                          • AZ
                          • Security Group
                          • Subnet
                          • VP CID
                          • Connection
                          • Node Class
                          • Role
                          • Storage Type
                          • Private IP Address
                          • EIP
                          • Parameter_Group
                          • Storage Space Usage
                          -

                          Exporting DB Instance Information

                          1. Log in to the DDS console.
                          2. On the Instance Management page, click in the upper right corner of the instance list.
                          3. In the pop-up box, select the desired items and click OK.
                          4. View the .xls file exported to your local PC.
                          +

                          Exporting DB Instance Information

                          1. Log in to the DDS console.
                          2. On the Instance Management page, click in the upper right corner of the instance list.
                          3. In the pop-up box, select the desired items and click OK.
                          4. View the .xls file exported to your local PC.
                          -

                          Export the specified instance on the current page.

                          1. Log in to the DDS console.
                          2. On the Instance Management page, click in the upper right corner of the instance list.
                          3. In the pop-up box, select the desired items and click OK.
                          4. View the .xls file exported to your local PC.
                          +

                          Export Specified Instance

                          1. Log in to the DDS console.
                          2. On the Instance Management page, select the target DB instance and click in the upper right corner of the instance list.
                          3. In the pop-up box, select the desired items and click OK.
                          4. View the .xls file exported to your local PC.
                          -
                          Parent topic: DB Instance Operations
                          +
                          Parent topic: Instance Management
                          diff --git a/docs/dds/umn/dds_03_0052.html b/docs/dds/umn/dds_03_0052.html index 6c4432f95..cbf33e7c1 100644 --- a/docs/dds/umn/dds_03_0052.html +++ b/docs/dds/umn/dds_03_0052.html @@ -1,49 +1,45 @@

                          Migrating Data

                          -

                          Scenarios

                          DDS supports access through EIPs by enabling public accessibility. You can also access a database through an ECS in the private network.

                          -

                          Before migrating data from a MongoDB database to DDS, transfer data to a .json file using the mongoexport tool. This section guides you on how to import the data from the JSON files to DDS using the mongoimport tool on the ECS or the device that can access DDS.

                          +

                          Scenarios

                          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 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.

                          -

                          Preparations

                          1. An ECS or a device that can access DDS is ready for use.
                            • To connect to a DDS DB instance from an ECS, you need to create and log in to the ECS. For details, see How Can I Create and Log In to an ECS?
                            • To bind an EIP to a DB instance:
                              1. Bind an EIP to a node in the DB instance. For details about how to bind an EIP to a node, see "Binding and Unbinding an EIP" in section "Cluster" or "Replica Set".
                              2. Ensure that your local device can access the EIP that has been bound to the DB instance.
                              +

                              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.

                                  +
                                • To connect to your DDS DB instance through an EIP:
                                  1. Bind an EIP to a node in the DB instance. For details about how to bind an EIP to a node, see "Binding an EIP" in the Document Database Service Getting Started.
                                  2. Ensure that your local device can access the EIP that has been bound to the DB instance.
                                -
                              2. A migration tool has been installed on the prepared ECS or the device.

                                For details on how to install the migration tool, see How Can I Install a MongoDB Client?

                                +
                              3. A migration tool has been installed on the prepared ECS.

                                For details on how to install the migration tool, see How Can I Install a MongoDB Client?

                                The MongoDB client provides the mongoexport and mongoimport tools.

                              -

                              Exporting Data

                              1. Log in to the ECS or the device that can access DDS.
                              2. Use the mongoexport tool to transfer data from the source database to a .json file.

                                The SSL connection is used as an example. If you select a common connection, delete --ssl --sslAllowInvalidCertificates from the following command.

                                -

                                ./mongoexport --host <DB_ADDRESS> --port <DB_PORT> --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase <AUTH_DB> -u <DB_USER> --db <DB_NAME> --collection <DB_COLLECTION> --out <DB_PATH>

                                +

                                Exporting Data (Linux example)

                                1. Log in to the ECS or the device that can access DDS.
                                2. Use the mongoexport tool to transfer data from the source database to a .json file.

                                  The SSL connection is used as an example. If you select an unencrypted connection, delete --ssl --sslAllowInvalidCertificates from the following command.

                                  +

                                  mongoexport --host <DB_ADDRESS> --port <DB_PORT> --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase <AUTH_DB> -u <DB_USER> --db <DB_NAME> --collection <DB_COLLECTION> --out <DB_PATH>

                                  • DB_ADDRESS indicates the database address.
                                  • DB_PORT indicates the database port.
                                  • AUTH_DB indicates the database for storing DB_USER information. Generally, this value is admin.
                                  • DB_USER indicates the database user.
                                  • DB_NAME indicates the name of the database from which data will be exported.
                                  • DB_COLLECTION indicates the collection of the database from which data will be exported.
                                  • DB_PATH indicates the path where the .json file is located.

                                  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/mongodb/export/exportfile.json

                                3. 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

                                4. Compress the exported .json file.

                                  gzip exportfile.json

                                  Compressing the file helps reduce the time needed to transmit all the data. The compressed file is exportfile.json.gz.

                                -

                                Importing Data

                                1. Log in to the ECS or the device that can access DDS.
                                2. Upload the data to be imported to the ECS or the device that can access DDS.

                                  Select an uploading method based on the OS you are using. In Linux, for example, run the following command:

                                  +

                                  Importing Data

                                  1. Log in to the ECS or the device that can access DDS.
                                  2. Upload the data to be imported to the ECS or the device that can access DDS.

                                    Select an uploading method based on the OS you are using. In Linux, for example, run the following command:

                                    scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>

                                    -
                                    • IDENTITY_FILE indicates the directory where the exportfile.json.gz file is located. The file access permission is 600.
                                    • REMOTE_USER indicates the ECS OS user.
                                    • REMOTE_ADDRESS indicates the ECS address.
                                    • REMOTE_DIR indicates the directory of the ECS to which the exportfile.json.gz file is uploaded.
                                    -

                                    In Windows, upload exportfile.json.gz to the ECS using file transfer tools.

                                    +
                                    • IDENTITY_FILE indicates the directory where the exportfile.json.gz file is located. The file access permission is 600.
                                    • REMOTE_USER indicates the ECS OS user.
                                    • REMOTE_ADDRESS indicates the ECS address.
                                    • REMOTE_DIR indicates the directory of the ECS to which the exportfile.json.gz file is uploaded.
                                    +

                                    In Windows, upload exportfile.json.gz to the ECS using file transfer tools.

                                  3. Decompress the package.

                                    gzip -d exportfile.json.gz

                                    -

                                  4. Import the JSON file to the DDS database.

                                    The SSL connection is used as an example. If you select a common connection, delete --ssl --sslAllowInvalidCertificates from the following command.

                                    -

                                    ./mongoimport --host <DB_ADDRESS> --port <DB_PORT> --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase <AUTH_DB> -u <DB_USER> --db <DB_NAME> --collection <DB_COLLECTION> --file <DB_PATH>

                                    -
                                    • DB_ADDRESS indicates the DB instance IP address.
                                    • DB_PORT indicates the database port.
                                    • AUTH_DB indicates the database that authenticates DB_USER. Generally, this value is admin.
                                    • DB_USER indicates the account name of the database administrator.
                                    • DB_NAME indicates the name of the database to which data will be imported.
                                    • DB_COLLECTION indicates the collection of the database to which data will be imported.
                                    • DB_PATH indicates the path where the .json file is located.
                                    +

                                  5. Import the JSON file to the DDS database.

                                    The SSL connection is used as an example. If you select an unencrypted connection, delete --ssl --sslAllowInvalidCertificates from the following command.

                                    +

                                    mongoimport --host <DB_ADDRESS> --port <DB_PORT> --ssl --sslAllowInvalidCertificates --type json --authenticationDatabase <AUTH_DB> -u <DB_USER> --db <DB_NAME> --collection <DB_COLLECTION> --file <DB_PATH>

                                    +
                                    • DB_ADDRESS indicates the DB instance IP address.
                                    • DB_PORT indicates the database port.
                                    • AUTH_DB indicates the database that authenticates DB_USER. Generally, this value is admin.
                                    • DB_USER indicates the account name of the database administrator.
                                    • DB_NAME indicates the name of the database to which data will be imported.
                                    • DB_COLLECTION indicates the collection of the database to which data will be imported.
                                    • DB_PATH indicates the path where the .json file is located.

                                    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

                                    -

                                  6. Check the result.

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

                                    +

                                    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

                                    +

                                  7. 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

                                -
                                -
                                -
                                Parent topic: Managing DDS DB Instances
                                -
                                -
                                diff --git a/docs/dds/umn/dds_03_0057.html b/docs/dds/umn/dds_03_0057.html index ec3d76e35..56073b566 100644 --- a/docs/dds/umn/dds_03_0057.html +++ b/docs/dds/umn/dds_03_0057.html @@ -1,24 +1,24 @@ -

                                Managing Database Accounts

                                -

                                Scenarios

                                This section guides you through how to create a database account and change the account password to manage the instances you created.

                                When creating a database account for a specified DB instance, you are advised to enable the SSL connection to improve data security.

                                +

                                Creating a Database Account Using Commands

                                +

                                Scenarios

                                This section describes how to create a database account and change the account password using commands after the DDS DB instances are created.

                                When creating a database account for a specified DB instance, you are advised to enable the SSL connection to improve data security.

                                -

                                Prerequisites

                                A DDS DB instance has been connected. +

                                Prerequisites

                                A DDS DB instance has been connected.
                                -

                                Account Description

                                To provide management services for DDS DB instances, users root, monitor, and backup are created when you create a DDS DB instance. Attempting to delete, rename, change the passwords, or change privileges for these accounts will result in errors.

                                +

                                Account Description

                                To manage DDS DB instances, users root, monitor, and backup are automatically created when you create a DDS DB instance. Attempting to delete, rename, change the passwords, or change privileges for these accounts will result in errors.

                                You can change the password of the database administrator rwuser and any accounts you create.

                                -

                                Setting Password Strength for Database Accounts

                                • The administrator password must meet the following password policy:
                                  • 8 to 32 characters in length
                                  • A combination of uppercase letters, lowercase letters, digits, and special characters: ~!@#%^*-_=+?
                                  -
                                • The DDS instance database uses comprehensive password security policies. The password of a DDS instance database account must meet the following conditions:
                                  • 8 to 32 characters in length
                                  • A combination of uppercase letters, lowercase letters, digits, and special characters: ~!@#%^*-_=+?
                                  +

                                  Setting Password Strength for Database Accounts

                                  • The administrator password must meet the following password policy:
                                    • Contains 8 to 32 characters.
                                    • Must be a combination of uppercase letters, lowercase letters, digits, and special characters: ~!@#%^*-_=+?
                                    +
                                  • The database user created on the client must meet the following password policy:
                                    • Contains 8 to 32 characters.
                                    • Must be a combination of uppercase letters, lowercase letters, digits, and special characters: ~@#%-_!*+=^?
                                  -

                                  When you create a DB instance, the system automatically checks your password strength. You can change the password as user rwuser. For security reasons, you are advised to set up a strong password.

                                  +

                                  When you create a DB instance, DDS automatically checks your password strength. You can change the password as user rwuser. For security reasons, you are advised to set up a strong password.

                                  -

                                  Creating an Account

                                  1. Run the following command to select the admin database:

                                    use admin

                                    -

                                  2. Run the following command to create a database account (user1 as an example):

                                    db.createUser({user: "user1", pwd: "Test_12345", passwordDigestor:"server", roles:[{role: "root", db: "admin"}]})

                                    -
                                    • server: indicates that the password is encrypted on the server.
                                    • Test_12345: indicates the example new password. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and special characters, such as ~@#%-_!*+=^?
                                    • roles restricts the rights of the account. If an empty array is specified, the account does not have any permission.
                                    +

                                    Creating an Account

                                    1. Log in to the DDS.
                                    2. Run the following command to select the admin database:

                                      use admin

                                      +

                                    3. Run the following command to create a database account (user1 as an example):

                                      db.createUser({user: "user1", pwd: "**********", passwordDigestor:"server", roles:[{role: "root", db: "admin"}]})

                                      +
                                      • server: indicates that the password is encrypted on the server.
                                      • roles restrict the rights of the account. If an empty array is specified, the account does not have any permission.

                                    4. Check the result:

                                      The account is successfully created if the following information is displayed:

                                      Successfully added user: {
         "user" : "user1",
@@ -32,18 +32,19 @@
 }

                                    -

                                    Changing a Password

                                    1. Run the following command to select the admin database:

                                      use admin

                                      -

                                    2. Uses user user1 as an example. Run the following command to change its password:

                                      db.updateUser("user1", {passwordDigestor:"server",pwd:"newPasswd12#"})

                                      -
                                      • server: indicates that the password is encrypted on the server.
                                      • newPasswd12#: indicates the example new password. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and special characters, such as ~@#%-_!*+=^?
                                      +

                                      Changing a Password

                                      1. Log in to the DDS.
                                      2. Run the following command to select the admin database:

                                        use admin

                                        +

                                      3. Uses user user1 as an example. Run the following command to change its password:

                                        db.updateUser("user1", {passwordDigestor:"server",pwd:"**********"})

                                        +

                                        server: indicates that the password is encrypted on the server.

                                      4. Check the setting result. The password is successfully changed if the following information is displayed:

                                        • Cluster
                                          mongos>
                                        • Replica set
                                          replica:PRIMARY>
                                          +
                                        • Single node
                                          replica:PRIMARY>

                                    -
                                    Parent topic: Managing DDS DB Instances
                                    +
                                    Parent topic: Account Management
                                    diff --git a/docs/dds/umn/dds_03_0060.html b/docs/dds/umn/dds_03_0060.html new file mode 100644 index 000000000..833b16075 --- /dev/null +++ b/docs/dds/umn/dds_03_0060.html @@ -0,0 +1,26 @@ + + +

                                    Creating a User and Granting Permissions

                                    +

                                    This section describes how to use IAM to implement fine-grained permissions control for your DDS resources. With IAM, you can:

                                    +
                                    • Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to DDS resources.
                                    • Grant only the permissions required for users to perform a task.
                                    • Entrust an account or cloud service to perform professional and efficient O&M on your DDS resources.
                                    +

                                    If your account does not need individual IAM users, then you may skip over this topic.

                                    +

                                    This section describes the procedure for granting permissions (see Figure 1).

                                    +

                                    Prerequisites

                                    Learn about the permissions (see Permissions Management) supported by DDS and choose policies or roles according to your requirements. For the system policies of other services, see Permissions Policies.

                                    +
                                    +

                                    Process Flow

                                    Figure 1 Process for granting DDS permissions
                                    +
                                    +
                                    1. Create a user group and assign permissions to it.

                                      Create a user group on the IAM console, and assign the DDS FullAccess policy to the group.

                                      +

                                      To use some interconnected services, you also need to configure permissions of such services.

                                      +

                                      For example, when using DAS to connect to a DB instance, you need to configure the DDS FullAccess and DAS FullAccess permissions.

                                      +
                                      +
                                    2. Create an IAM user and add it to a user group.

                                      Create a user on the IAM console and add the user to the group created in 1.

                                      +
                                    3. Log in and verify permissions.

                                      Log in to the DDS console by using the newly created user, and verify that the user only has read permissions for DDS.

                                      +

                                      Choose Service List > Document Database Service and click Buy DB Instance. If you can buy a DDS DB instance, the required permission policies have taken effect.

                                      +
                                    +
                                    +
                                    +
                                    +
                                    Parent topic: Permissions Management
                                    +
                                    +
                                    + diff --git a/docs/dds/umn/dds_03_0061.html b/docs/dds/umn/dds_03_0061.html new file mode 100644 index 000000000..59142781c --- /dev/null +++ b/docs/dds/umn/dds_03_0061.html @@ -0,0 +1,78 @@ + + +

                                    Creating a Custom Policy

                                    +

                                    Custom policies can be created as a supplement to the system policies of DDS. For the actions supported for custom policies, see DDS Actions.

                                    +

                                    You can create custom policies in either of the following ways:

                                    +
                                    • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
                                    • JSON: Edit JSON policies from scratch or based on an existing policy.
                                    +

                                    For details, see Creating a Custom Policy. The following section contains examples of common DDS custom policies.

                                    +

                                    Example Custom Policies

                                    • Example 1: Allowing users to create DDS DB instances
                                      {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dds:instance:create"
+            ]
+        }
+    ]
+}
                                      +
                                    • Example 2: Denying DDS DB instance deletion

                                      A deny policy must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

                                      +

                                      The following method can be used if you need to assign permissions of the DDS FullAccess policy to a user but also forbid the user from deleting DDS DB instances. Create a custom policy for denying DDS DB instance deletion, and assign both policies to the group the user belongs to. Then the user can perform all operations on DDS except deleting DDS instances. The following is an example deny policy:

                                      +
                                      {
+    "Version": "1.1",
+    "Statement": [
+        {
+          "Effect": "Deny"
+          "Action": [
+                "dds:instance:deleteInstance"
+            ],
+          }
+    ]
+}
                                      +
                                    • Example 3: Defining permissions for multiple services in a policy

                                      A custom policy can contain actions of multiple services that are all of the global or project-level type. The following is an example policy containing actions of multiple services:

                                      +
                                      {  
+        "Version": "1.1",  
+        "Statement": [  
+                {  
+                        "Action": [  
+                                "dds:instance:create",  
+                                "dds:instance:modify",  
+                                "dds:instance:deleteInstance",  
+                 "vpc:publicIps:list",  
+                 "vpc:publicIps:update"  
+                        ],  
+                        "Effect": "Allow"  
+                }  
+        ]  
+}
+Example 4: Setting resource policies
+A custom policy can be used to set resource policies, indicating the operation permissions on the resources under the current action. Currently, the instance name can be configured, and the asterisk (*) can be used as a wildcard. The following is an example resource policy:
+{
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dds:instance:list"
+            ]
+        },
+        {
+            "Effect": "Allow",
+            "Action": [
+                "dds:instance:modify"
+            ],
+            "Resource": [
+                "DDS:*:*:instanceName:dds-*"
+            ]
+        }
+    ]
+}
                                      +
                                    +
                                    +
                                    +
                                    +
                                    +
                                    Parent topic: Permissions Management
                                    +
                                    +
                                    + diff --git a/docs/dds/umn/dds_03_0062.html b/docs/dds/umn/dds_03_0062.html new file mode 100644 index 000000000..8ad7c375d --- /dev/null +++ b/docs/dds/umn/dds_03_0062.html @@ -0,0 +1,14 @@ + + +

                                    Permissions Management

                                    +

                                    +
                                    + + diff --git a/docs/dds/umn/dds_03_0064.html b/docs/dds/umn/dds_03_0064.html new file mode 100644 index 000000000..2812f041f --- /dev/null +++ b/docs/dds/umn/dds_03_0064.html @@ -0,0 +1,23 @@ + + +

                                    Restoring Replica Set Instance to a Point in Time

                                    +

                                    Scenarios

                                    You can restore the data of a replica set instance to a specified time point.

                                    +
                                    +

                                    Restoration Precautions

                                    • Currently, you can restore a replica set instance to a new or original DB instance at a point in time.
                                    • In case of point-in-time recovery, the "local" database (which is a default database in DDS instances) will not be restored.
                                    • When you enter the time point that you want to restore the DB instance to, DDS downloads the latest full backup file before the specified time point from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.
                                    +
                                    +

                                    Constraints

                                    Data can be restored to a specified time point only after the automated backup policy is enabled.

                                    +
                                    +

                                    Procedure

                                    1. Log in to the DDS console.
                                    2. On the Instance Management page, click the target replica set instance.
                                    3. In the navigation pane on the left, click Backups & Restorations.
                                    4. On the Backups & Restorations page, click Restore to Point In Time.
                                    5. Select the date and time range, select or enter a time point within the acceptable range, and select Create New Instance or Restore to Original.
                                    6. On the displayed page, the DB instance is restored based on the restoration method you selected in 5.

                                      • 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, and storage type must be the same as those of the original and cannot be changed.
                                        • The storage space is the same as that of the original instance by default. You can only increase the storage space.
                                        +
                                      • 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.
                                        +
                                        +
                                      +

                                    +
                                    +
                                    +
                                    +
                                    +
                                    Parent topic: Backup and Restore
                                    +
                                    +
                                    + diff --git a/docs/dds/umn/dds_03_0070.html b/docs/dds/umn/dds_03_0070.html new file mode 100644 index 000000000..29dde0cde --- /dev/null +++ b/docs/dds/umn/dds_03_0070.html @@ -0,0 +1,17 @@ + + +

                                    Changing a Private IP Address

                                    +

                                    Scenarios

                                    After a database is migrated from on-premises or other cloud platforms to DDS, the private IP address of the database may be changed. DDS allows you to change the private IP address, reducing migration costs.

                                    +
                                    +

                                    Constraints

                                    Changing the private IP address of a node will invalidate the previous private IP address. After the change, the new private IP address is bound to the EIP.

                                    +
                                    +

                                    Procedure

                                    1. Log in to the DDS console.
                                    2. In the left navigation pane, choose Instance Management. In the DB instance list, click the target cluster instance to go to the Basic Information page.

                                      Alternatively, on the Basic Information page, in the navigation pane on the left, click Connections.

                                      +

                                    3. In the Node Information area, locate the target node and in the Operation column, click Change Private IP Address.
                                    4. In the displayed dialog box, enter a private IP address that is not in use and click OK.
                                    5. In the Node Information area, locate the target node and view the new private IP address.
                                    +
                                    +
                                    +
                                    +
                                    +
                                    Parent topic: Connection Management
                                    +
                                    +
                                    + diff --git a/docs/dds/umn/dds_03_0074.html b/docs/dds/umn/dds_03_0074.html new file mode 100644 index 000000000..81fd81d4c --- /dev/null +++ b/docs/dds/umn/dds_03_0074.html @@ -0,0 +1,21 @@ + + +

                                    Enabling or Disabling SSL

                                    +

                                    Scenarios

                                    DDS allows you to use SSL to encrypt connections to a DB instance to protect your data.

                                    +
                                    • If SSL is enabled, you can connect to a DB instance using SSL. For details, see sections about connecting to a DB instance using SSL over public or private networks in this document.
                                    • If SSL is disabled, you can connect to the DB instance using an unencrypted connection. For details, see sections about connecting to a DB instance using an unencrypted connection over public or private networks in this document.
                                    +
                                    • For security purposes, disabling SSL is not advised.
                                    • Enabling or disabling SSL will cause DB instance restart. Exercise caution when you perform this operation.
                                    +
                                    +
                                    +

                                    Enabling SSL

                                    1. On the Instance Management page, click the target DB instance.
                                    2. In the DB Information area on the Basic Information page, click next to the SSL field.

                                      Alternatively, in the navigation pane on the left, choose Connections. In the Basic Information area, click next to the SSL field.

                                      +

                                    3. In the displayed dialog box, click Yes.
                                    4. In the Basic Information area, view the modification result.
                                    +
                                    +

                                    Disabling SSL

                                    1. On the Instance Management page, click the target DB instance.
                                    2. In the DB Information area on the Basic Information page, click next to the SSL field.

                                      Alternatively, in the navigation pane on the left, choose Connections. In the Basic Information area, click next to the SSL field.

                                      +

                                    3. In the displayed dialog box, click Yes.
                                    4. In the Basic Information area, view the modification result.
                                    +
                                    +
                                    +
                                    +
                                    +
                                    Parent topic: Connection Management
                                    +
                                    +
                                    + diff --git a/docs/dds/umn/dds_03_0075.html b/docs/dds/umn/dds_03_0075.html index dc719d32f..8281ce864 100644 --- a/docs/dds/umn/dds_03_0075.html +++ b/docs/dds/umn/dds_03_0075.html @@ -1,18 +1,18 @@ -

                                    Modifying the DB Instance Name

                                    -

                                    Scenarios

                                    This section guides you on how to modify the DB instance name to identify different DB instances.

                                    +

                                    Changing a DB Instance Name

                                    +

                                    Scenarios

                                    This section describes how to change a DB instance name to identify different DB instances.

                                    -

                                    Method 1

                                    1. Log in to the DDS console.
                                    2. On the Instance Management page, click next to the specified DB instance name.

                                      • If you want to submit the change, click OK. 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 (_).
                                      • If you want to cancel the change, click Cancel.
                                      +

                                      Method 1

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, hover the mouse over the DDS instance name you wish to change and click the icon that is displayed next to the DB instance.

                                        • If you want to submit the change, click OK. 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 (_).
                                        • If you want to cancel the change, click Cancel.

                                      3. View the change result on the Instance Management page.
                                      -

                                      Method 2

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the target DB instance.
                                      3. In the DB Information area on the Basic Information page, click in the DB Instance Name field to change the instance name.

                                        • If you want to submit the change, click . 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 (_).
                                        • If you want to cancel the change, click .
                                        -

                                      4. View the modification result.
                                      +

                                      Method 2

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the target DB instance.
                                      3. In the DB Information area on the Basic Information page, click in the DB Instance Name field to change the instance name.

                                        • To submit the change, click . 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 (_).
                                        • To cancel the change, click .
                                        +

                                      4. View the results on the Instance Management page.
                                      -
                                      Parent topic: DB Instance Operations
                                      +
                                      Parent topic: Instance Management
                                      diff --git a/docs/dds/umn/dds_03_0076.html b/docs/dds/umn/dds_03_0076.html new file mode 100644 index 000000000..343fbe059 --- /dev/null +++ b/docs/dds/umn/dds_03_0076.html @@ -0,0 +1,22 @@ + + +

                                      Viewing DDS Metrics

                                      +

                                      Scenarios

                                      Cloud Eye monitors DDS instance metrics. You can obtain the monitoring metrics of DDS on the management console.

                                      +

                                      Monitored data requires a period of time for transmission and display.

                                      +
                                      +

                                      Prerequisites

                                      • Cloud Eye does not display the metrics of a deleted DB instance or node. You can view the monitoring information only after the instance is restarted or recovered.
                                      +
                                      • The DDS instance metrics are displayed on the Cloud Eye page with 5-10 minutes delay.
                                      +
                                      +

                                      Method 1

                                      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, choose Advanced O&M.
                                      4. On the Real-Time Monitoring tab, view metrics of DDS instances and/or instance specific nodes if there are any.
                                      5. On the Real-Time Monitoring tab, you can select a duration to view the monitoring data.

                                        • You can view the monitoring data of the last 1 hour, 3 hours, and 12 hours.
                                        • After the automatic refresh function is enabled, monitoring data is automatically refreshed at an interval of 60s.
                                        • For more metric information, click View details to switch to the Cloud Eye console.
                                        +

                                      +
                                      +

                                      Method 2

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Under Management & Deployment, click Cloud Eye.
                                      4. In the navigation pane on the left, choose Cloud Service Monitoring > Document Database Service.
                                      5. On the displayed page, locate the target instance and click View Metric in the Operation column.
                                      6. In the DDS monitoring area, you can select a duration to view the monitoring data.

                                        You can view the monitoring data of DDS in the recent 1 hour, 3 hours, or 12 hours. To view the monitoring curve of a longer time range, click to enlarge the graph.

                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Monitoring and Alarm Reporting
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_0078.html b/docs/dds/umn/dds_03_0078.html deleted file mode 100644 index 0c14040c7..000000000 --- a/docs/dds/umn/dds_03_0078.html +++ /dev/null @@ -1,23 +0,0 @@ - - -

                                      Viewing DDS Metrics

                                      -

                                      Scenarios

                                      Cloud Eye monitors DDS running statuses. You can obtain the monitoring metrics of DDS on the management console.

                                      -

                                      Monitored data requires a period of time for transmission and display. The status of DDS displayed on the Cloud Eye page is the status obtained 5 to 10 minutes before. You can view the monitored data of a newly created DB instance 5 to 10 minutes later.

                                      -
                                      -

                                      Prerequisites

                                      • The DDS DB instance is running properly.

                                        Cloud Eye does not display the metrics of a faulty or deleted DB instance or node. You can view the monitoring information only after the instance is restarted or recovered.

                                        -
                                      -

                                      Cloud Eye will delete a DDS DB instance or node that becomes faulty for 24 hours from the monitoring list and will not monitor it any more. However, you need to manually clear its alarm rules.

                                      -
                                      -
                                      • The DB instance has been properly running for at least 10 minutes.

                                        For a newly created DB instance, you need to wait for a while before viewing the monitoring metrics.

                                        -
                                      -
                                      -

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Under Management & Deployment, click Cloud Eye.
                                      4. In the navigation pane on the left, choose Cloud Service Monitoring > Document Database Service.
                                      5. On the displayed page, locate the target instance and click View Metric in the Operation column.
                                      6. In the DDS monitoring area, you can select a duration to view the monitoring data.

                                        You can view the monitoring data of DDS in the recent 1 hour, 3 hours, or 12 hours. To view the monitoring curve of a longer time range, click to enlarge the graph.

                                        -

                                      -
                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Interconnected with Cloud Eye
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_03_0080.html b/docs/dds/umn/dds_03_0080.html new file mode 100644 index 000000000..a34ca2560 --- /dev/null +++ b/docs/dds/umn/dds_03_0080.html @@ -0,0 +1,11 @@ + + +

                                      Database Commands

                                      +
                                      + + diff --git a/docs/dds/umn/dds_03_0100.html b/docs/dds/umn/dds_03_0100.html new file mode 100644 index 000000000..c2c7598e7 --- /dev/null +++ b/docs/dds/umn/dds_03_0100.html @@ -0,0 +1,21 @@ + + +

                                      Configuring Cross-CIDR Access for Replica Set Instances

                                      +

                                      If a client and a replica set instance are deployed in different CIDR blocks and the client is not in 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8, configure Cross-CIDR Access for the instance to communicate with the client.

                                      +

                                      Precautions

                                      • During the configuration of cross-CIDR access, services are running properly without interruption or intermittent disconnection.
                                      • If the client and replica set instance are in different VPCs and CIDR blocks, configure a VPC peering connection by referring to VPC Peering Connection in Virtual Private Cloud User Guide.
                                      +
                                      +

                                      Procedure

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the target replica set instance.
                                      3. In the navigation pane on the left, choose Connections.
                                      4. On the Address area, click Enable to the right of Cross-CIDR Access and specify the client CIDR block details.

                                        Up to 30 CIDR blocks can be configured, and each of them can overlap but they cannot be the same. That is, the source CIDR blocks can overlap but cannot be the same.

                                        +
                                        +

                                      5. After cross-CIDR access is enabled, Enabled is displayed to the right of Cross-CIDR Access.

                                        If you need to change the client CIDR block, click Change to the right of Cross-CIDR Access.

                                        +
                                        • To ensure the ECS and the DB instance can communicate with each other, configure the connection by referring to section "VPC Peering Connection Overview" in the Virtual Private Cloud User Guide.
                                        +
                                        +
                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Connection Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_0101.html b/docs/dds/umn/dds_03_0101.html new file mode 100644 index 000000000..d177e1e68 --- /dev/null +++ b/docs/dds/umn/dds_03_0101.html @@ -0,0 +1,25 @@ + + +

                                      Recycling a DB Instance

                                      +

                                      DDS can move deleted DB instances to the recycle bin, so you can restore them easily.

                                      +

                                      Precautions

                                      • The recycling policy is enabled by default and cannot be disabled. Instances in the recycle bin are retained for 7 days by default, and this will not generate any charges.
                                      +
                                      +
                                      • Up to 100 instances can be moved to the recycle bin. Once the recycle bin is full, you can still delete instances, but they cannot be placed in the recycle bin, so the deletions will be permanent.
                                      +

                                      Modifying the Recycling Policy

                                      You can modify the retention period, and the changes only apply to the DB instances deleted after the changes, so exercise caution when performing this operation.

                                      +
                                      +
                                      1. Log in to the DDS console.
                                      2. In the navigation pane on the left, choose Recycling Management.
                                      3. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days. Then, click OK.
                                      +
                                      +

                                      Rebuilding a DB Instance

                                      You can rebuild DB instances from the recycle bin within the retention period to restore data.

                                      +
                                      1. Log in to the DDS console.
                                      2. In the navigation pane on the left, choose Recycling Management.
                                      3. On the Recycling Management page, locate the DB instance to be rebuilt and in the Operation column, click Rebuild.
                                      4. On the displayed page, set required parameters and submit the rebuilding task.

                                        • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
                                        • 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 the following sections. +
                                        • A full backup is triggered after the new instance is created.
                                        +

                                        After the instance has been rebuilt, it also stays in the recycle bin and cannot be deleted.

                                        +
                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Instance Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_0110.html b/docs/dds/umn/dds_03_0110.html new file mode 100644 index 000000000..87113f201 --- /dev/null +++ b/docs/dds/umn/dds_03_0110.html @@ -0,0 +1,18 @@ + + +

                                      Viewing Parameter Change History

                                      +

                                      You can view the change history of a parameter template.

                                      +

                                      Precautions

                                      In a newly exported or created parameter template, the change history is blank.

                                      +
                                      +

                                      Viewing Change History of a Custom Parameter Template

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                      4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click its name.
                                      5. In the navigation pane on the left, choose Change History. Then, view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                        You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

                                        +

                                      +
                                      +

                                      Viewing Change History of DB Instance Parameters

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                      4. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                      5. In the navigation pane on the left, click Parameters. On the Change History tab, view the parameter name, original parameter value, new parameter value, modification status, and modification time.
                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Parameter Template Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_0111.html b/docs/dds/umn/dds_03_0111.html new file mode 100644 index 000000000..6ae4bd801 --- /dev/null +++ b/docs/dds/umn/dds_03_0111.html @@ -0,0 +1,21 @@ + + +

                                      Exporting a Parameter Template

                                      +
                                      • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to other instances by referring to Applying a Parameter Template.
                                      • You can export parameter template details (parameter names, values, and descriptions) of an instance to a CSV file for review and analysis.
                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                      4. In the navigation pane on the left, choose Instance Management. On the displayed page, click the target instance. The Basic Information page is displayed.
                                      5. In the navigation pane on the left, choose Parameters. On the Parameters tab, above the parameter list, click Export.

                                        • Exporting to a custom template Export the parameter list of the instance to a parameter template for future use.
                                          In the displayed dialog box, configure required details and click OK.
                                          • New Parameter Template: The template name can be 4 to 64 characters long and starts with a letter. It can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
                                          • Description: The template description consists of a maximum of 256 characters and cannot include line breaks or the following special characters: >!<"&'=
                                          +
                                          +
                                          +

                                          After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

                                          +
                                        • Exporting to a file: You can export the parameter template details (parameter names, values, and descriptions) of a DB instance to a CSV file for review and analysis.
                                          In the displayed dialog box, enter the file name and click OK.

                                          The file name must start with a letter and consist of 4 to 81 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                                          +
                                          +
                                          +
                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Parameter Template Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_0113.html b/docs/dds/umn/dds_03_0113.html new file mode 100644 index 000000000..8a5eeb058 --- /dev/null +++ b/docs/dds/umn/dds_03_0113.html @@ -0,0 +1,14 @@ + + +

                                      Viewing Application Records of a Parameter Template

                                      +

                                      An application record contains information about performed apply operations. You can view the application records of a parameter template.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                      4. In the navigation pane on the left, click Parameter Template Management.
                                      5. On the Parameter Template Management page, select the parameter template for which you want to view application records.

                                        • Click Default Templates. Locate the target parameter template and click View Application Record.
                                        • Click Custom Templates. Locate the target parameter template and choose More > View Application Record.
                                        +

                                      6. You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and the causes of any failures that have occurred.
                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Parameter Template Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_change_database_port.html b/docs/dds/umn/dds_03_change_database_port.html new file mode 100644 index 000000000..bf83a98d5 --- /dev/null +++ b/docs/dds/umn/dds_03_change_database_port.html @@ -0,0 +1,19 @@ + + +

                                      Changing the Database Port

                                      +

                                      Scenarios

                                      This section guides you on how to modify the database port. The database port cannot be changed when the instance is in any of the following statuses:

                                      +
                                      • Restarting
                                      • Adding node
                                      • Switching SSL
                                      • Changing instance class
                                      • Deleting node
                                      • Creation failed
                                      +
                                      • Creating
                                      +
                                      +

                                      Procedure

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the target DB instance. The Basic Information page is displayed.
                                      3. In the Network Information area, click to right of the Database Port field.

                                        Alternatively, in the navigation pane on the left, choose Connections.

                                        +

                                      4. In the Basic Information area, click to right of the Database Port field.

                                        The database port range is 2100 to 9500.

                                        +
                                        • To submit the change, click . This process takes about 1 to 5 minutes.
                                        • To cancel the change, click .
                                        +

                                      5. View the modification result.
                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Connection Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_change_security_group.html b/docs/dds/umn/dds_03_change_security_group.html new file mode 100644 index 000000000..8dffb2ddd --- /dev/null +++ b/docs/dds/umn/dds_03_change_security_group.html @@ -0,0 +1,19 @@ + + +

                                      Changing a Security Group

                                      +

                                      Scenarios

                                      This section guides you on how to change a security group for cluster, replica set, and single node instances. If any of the following operations is in progress, do not change the security group:

                                      +
                                      • Adding nodes
                                      • Migrating data
                                      +
                                      +

                                      Procedure

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the instance name. The Basic Information page is displayed.
                                      3. In the Network Information area on the Basic Information page, click to select the security group to which the DB instance belongs.

                                        You can also choose Connections in the navigation pane on the left. On the Private Connection tab, in the Security Group area, click to select the security group to which the DB instance belongs.

                                        Ensure that the new security group does not affect the DB instance connection. Otherwise, the connection may be interrupted.

                                        +
                                        +
                                        • To submit the change, click . This process takes about 1 to 3 minutes.
                                        • To cancel the change, click .
                                        +
                                        +

                                      4. View the modification result.
                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Connection Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_03_reset_password.html b/docs/dds/umn/dds_03_reset_password.html new file mode 100644 index 000000000..a09349f37 --- /dev/null +++ b/docs/dds/umn/dds_03_reset_password.html @@ -0,0 +1,20 @@ + + +

                                      Resetting the Administrator Password

                                      +

                                      Scenarios

                                      For security reasons, you are advised to periodically change administrator passwords.

                                      +

                                      You cannot reset the administrator password under the following circumstances:

                                      +
                                      +
                                      • Restarting
                                      • Adding node
                                      • Switching SSL
                                      • Changing port
                                      • Changing instance class
                                      • Deleting node
                                      +

                                      Method 1

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, locate the target DB instance and choose More > Reset Password in the Operation column.
                                      3. Enter and confirm the new administrator password and click OK.

                                        The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

                                        +

                                      +
                                      +

                                      Method 2

                                      1. Log in to the DDS console.
                                      2. On the Instance Management page, click the target DB instance.
                                      3. In the DB Information area on the Basic Information page, click Reset Password to the right of the Administrator field.
                                      4. Enter and confirm the new administrator password and click OK.

                                        The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Account Management
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_08_0001.html b/docs/dds/umn/dds_08_0001.html deleted file mode 100644 index af764775d..000000000 --- a/docs/dds/umn/dds_08_0001.html +++ /dev/null @@ -1,18 +0,0 @@ - - -

                                      Changing DB Instance Classes

                                      -

                                      -
                                      - - diff --git a/docs/dds/umn/dds_change_history.html b/docs/dds/umn/dds_change_history.html index 527030798..f64642c75 100644 --- a/docs/dds/umn/dds_change_history.html +++ b/docs/dds/umn/dds_change_history.html @@ -2,189 +2,258 @@

                                      Change History

                                      -

                                      Released On

                                      +
                                      - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dds/umn/dds_faq_0001.html b/docs/dds/umn/dds_faq_0001.html index aae0097b6..6f58bc40f 100644 --- a/docs/dds/umn/dds_faq_0001.html +++ b/docs/dds/umn/dds_faq_0001.html @@ -1,14 +1,13 @@

                                      What Precautions Should Be Taken When Using DDS?

                                      -
                                      1. Failover

                                        DDS uses multiple mongos, replica sets, and shards to ensure data reliability. When a mongos is faulty, the other mongos takes over services immediately to ensure service continuity. A replica set consists of a primary, a secondary, and a hidden node. When the primary node is faulty, DDS selects the secondary node as the new primary within 30 seconds.

                                        -
                                      2. ECSs used for DB instances are invisible to you. Your applications can access the IP addresses and ports corresponding to the database only.
                                      3. Backup files stored on OBS are invisible to you. They are only visible in the DDS backend management system.
                                      4. Precautions after applying for DDS:

                                        After purchasing DDS DB instances, you do not need to perform basic database O&M operations, such as HA and security patches. You need to pay attention to the following:

                                        +
                                        1. Precautions after applying for DDS:

                                          After purchasing DDS DB instances, you do not need to perform basic database O&M operations, such as HA and security patches. You need to pay attention to the following:

                                          1. Whether the vCPUs, IOPS, and storage space for DDS DB instances are sufficient. If any of them is insufficient, optimize or upgrade the related configuration.
                                          2. Whether the performance of DDS DB instances is satisfying, whether a large number of slow query statements exist, whether query statements need to be optimized, and whether any index is redundant or missing.
                                        -
                                        Parent topic: Common FAQs
                                        +
                                        Parent topic: Product Consulting
                                        diff --git a/docs/dds/umn/dds_faq_0002.html b/docs/dds/umn/dds_faq_0002.html index 95736a4ee..b2e97b3e0 100644 --- a/docs/dds/umn/dds_faq_0002.html +++ b/docs/dds/umn/dds_faq_0002.html @@ -6,7 +6,7 @@
                                      -
                                      Parent topic: Common FAQs
                                      +
                                      Parent topic: Product Consulting
                                      diff --git a/docs/dds/umn/dds_faq_0003.html b/docs/dds/umn/dds_faq_0003.html deleted file mode 100644 index 87de04acb..000000000 --- a/docs/dds/umn/dds_faq_0003.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                                      Can I Use a Template to Create DDS DB Instances?

                                      -

                                      You do not need a template to create DDS DB instances. When you create a DB instance, DDS provides different DB instance specifications which are similar to templates.

                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Common FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0004.html b/docs/dds/umn/dds_faq_0004.html index 56d41dadd..d60ac6d63 100644 --- a/docs/dds/umn/dds_faq_0004.html +++ b/docs/dds/umn/dds_faq_0004.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Common FAQs
                                      +
                                      Parent topic: Product Consulting
                                      diff --git a/docs/dds/umn/dds_faq_0005.html b/docs/dds/umn/dds_faq_0005.html index 3d15340ba..98e079535 100644 --- a/docs/dds/umn/dds_faq_0005.html +++ b/docs/dds/umn/dds_faq_0005.html @@ -3,11 +3,11 @@

                                      What Should I Do If My Query Is Slow?

                                      • You can view the slow query logs to check whether any slowly executed SQL queries exist and view the performance characteristics of queries (if any) to locate the cause of slow queries.

                                        For details on DDS log queries, see section Slow Query Log.

                                      -
                                      • You can also view CPU usage metrics of DDS DB instances to facilitate problem locating. For details, see section Viewing DDS Metrics.
                                      +
                                      • You can also view CPU usage metrics of DDS DB instances to facilitate problem locating. For details, see section Viewing DDS Metrics.
                                      -
                                      Parent topic: Management FAQs
                                      +
                                      Parent topic: Database Performance
                                      diff --git a/docs/dds/umn/dds_faq_0006.html b/docs/dds/umn/dds_faq_0006.html index 3e903a8f7..8a10cff2f 100644 --- a/docs/dds/umn/dds_faq_0006.html +++ b/docs/dds/umn/dds_faq_0006.html @@ -4,11 +4,11 @@

                                      The delay for primary/secondary synchronization cannot be calculated using a formula. The delay is affected by the following factors:

                                      1. Network communication status
                                      2. Transaction pressure on the primary node, that is, transactions per second (TPS) of the primary node
                                      3. Transaction size executed by the primary node, that is, the duration of a transaction execution
                                      4. Load of the secondary node

                                      If the primary node bears heavy pressure within a period and executes a large number of transactions per second, the synchronization to the secondary node is delayed.

                                      -

                                      You can view Delay Between Primary and Secondary Nodes of the secondary node on the Cloud Eye console to know the synchronization delay.

                                      +

                                      You can view Replication Lag of the secondary node on the Cloud Eye console to know the synchronization delay.

                                      -
                                      Parent topic: Management FAQs
                                      +
                                      Parent topic: Database Performance
                                      diff --git a/docs/dds/umn/dds_faq_0007.html b/docs/dds/umn/dds_faq_0007.html index eeba55b74..5eccdb1df 100644 --- a/docs/dds/umn/dds_faq_0007.html +++ b/docs/dds/umn/dds_faq_0007.html @@ -3,11 +3,11 @@

                                      Why Is Data Missing from My Database?

                                      DDS does not delete or perform any operations on any user data. If this problem occurs, check whether a misoperation has been performed. Restore the data using backup files, if necessary.

                                      Solution:

                                      - +
                                      • Use the DDS restoration function to restore data. For details, see chapter "Backup and Restore" in the Document Database Service User Guide.
                                      • Import backups to DDS. For details, see section Migrating Data.
                                      -
                                      Parent topic: Management FAQs
                                      +
                                      Parent topic: Creation and Deletion
                                      diff --git a/docs/dds/umn/dds_faq_0008.html b/docs/dds/umn/dds_faq_0008.html index 041647813..61f208664 100644 --- a/docs/dds/umn/dds_faq_0008.html +++ b/docs/dds/umn/dds_faq_0008.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Management FAQs
                                      +
                                      Parent topic: Creation and Deletion
                                      diff --git a/docs/dds/umn/dds_faq_0009.html b/docs/dds/umn/dds_faq_0009.html index 4df8f88d4..472112321 100644 --- a/docs/dds/umn/dds_faq_0009.html +++ b/docs/dds/umn/dds_faq_0009.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Management FAQs
                                      +
                                      Parent topic: Database Usage
                                      diff --git a/docs/dds/umn/dds_faq_0010.html b/docs/dds/umn/dds_faq_0010.html deleted file mode 100644 index 96d91fe96..000000000 --- a/docs/dds/umn/dds_faq_0010.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                                      Does DDS Support Read/Write Splitting?

                                      -

                                      Yes. DDS can perform write operations only on the primary node in a replica set. You can configure DDS to perform read operations on the secondary node to split read and write operations.

                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Management FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0011.html b/docs/dds/umn/dds_faq_0011.html deleted file mode 100644 index d44462f8f..000000000 --- a/docs/dds/umn/dds_faq_0011.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                                      Can an External Server Access the DDS DB Instance?

                                      -

                                      You can access the DDS DB instance using the following methods:

                                      -
                                      • Create a DDS DB instance and an ECS in the same VPC to enable the ECS to access the instance.
                                      • If the DDS DB instance has an EIP assigned, you can access the instance through the EIP.
                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Connection and Access FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0012.html b/docs/dds/umn/dds_faq_0012.html index a20b364c7..da7a71d85 100644 --- a/docs/dds/umn/dds_faq_0012.html +++ b/docs/dds/umn/dds_faq_0012.html @@ -1,11 +1,12 @@

                                      What Is the Number of DDS Database Connections?

                                      -

                                      The number of DDS database connections indicates the number of applications that can be simultaneously connected to the database. Generally, it indicates the number of connections to mongos. The number of DDS connections is irrelevant to the maximum number of users allowed by applications or websites.

                                      +

                                      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.
                                      -
                                      Parent topic: Connection and Access FAQs
                                      +
                                      Parent topic: Database Connection
                                      diff --git a/docs/dds/umn/dds_faq_0013.html b/docs/dds/umn/dds_faq_0013.html index 5edee92c9..1827a9bb1 100644 --- a/docs/dds/umn/dds_faq_0013.html +++ b/docs/dds/umn/dds_faq_0013.html @@ -1,16 +1,24 @@ -

                                      What Should I Do If the ECS Cannot Connect to a DDS DB Instance?

                                      -

                                      Perform the following steps to identify the problem: The following uses the cluster instance as an example.

                                      -
                                      1. Check whether the ECS and DDS DB instance are located in the same VPC.

                                        • If they are in the same VPC, go to 2.
                                        • If they are in different VPCs, create an ECS in the VPC where the DDS DB instance is located.
                                        -

                                      2. Check whether a security group has been added to the ECS.

                                        • If yes, check whether its configuration rules are suitable. For details, see the security group description in section Setting a Security Group. Then, go to 3.
                                        • If no security group has been added, go to the VPC console from the ECS details page and click Security Groups to add a security group.
                                        -

                                      3. On the ECS, check whether the DDS DB instance address port can be connected.

                                        telnet <DB instance address> {8635}
                                        -
                                        • If the port can be connected, the network is normal. Check the database account and password. For details, see section Connecting to a DB Instance Through a Client.
                                        • If the port cannot be connected, contact post-sales technical support for troubleshooting.
                                        +

                                        What Should I Do If an ECS Cannot Connect to a DDS DB Instance?

                                        +

                                        Perform the following steps to identify the problem:

                                        +

                                        Replica Set Instance

                                        1. Check whether the ECS and replica set instance are in the same VPC.

                                          • If yes, go to 3.
                                          • If no, configure the VPC peering connection. For details, see "VPC Peering Connection" in Virtual Private Cloud User Guide. Then, go to 2.
                                          +

                                        2. Check whether the client and replica set instance are deployed in different CIDR blocks and whether the CIDR block of the client is not 192.168.0.0/16, 172.16.0.0/24, or 10.0.0.0/8.

                                          +

                                        3. Check whether a security group has been associated with the ECS.

                                          • If yes, check whether the security group rules are suitable. For details, see Setting a Security Group. Then, go to 4.
                                          • If no, go to the VPC console from the ECS details page and click Security Groups to add a security group.
                                          +

                                        4. On the ECS, check whether the DDS instance address port can be connected.

                                          telnet <DB instance address> {8635}
                                          +

                                        +

                                        Cluster and Single Node Instances

                                        1. Check whether the ECS and DDS instance are located in the same VPC.

                                          • If yes, go to 2.
                                          • If no, create an ECS in the VPC where the DDS instance is located.
                                          +

                                        2. Check whether a security group has been associated with the ECS.

                                          • If yes, check whether the security group rules are suitable. For details, see Setting a Security Group. Then, go to 3.
                                          • If no, go to the VPC console from the ECS details page and click Security Groups to add a security group.
                                          +

                                        3. On the ECS, check whether the DDS instance address port can be connected.

                                          telnet <DB instance address> {8635}
                                          + +

                                        +
                                        +
                                        -
                                        Parent topic: Connection and Access FAQs
                                        +
                                        Parent topic: Database Connection
                                        diff --git a/docs/dds/umn/dds_faq_0014.html b/docs/dds/umn/dds_faq_0014.html deleted file mode 100644 index 92c5d28f8..000000000 --- a/docs/dds/umn/dds_faq_0014.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

                                        What Should I Do If a Database Client Problem Causes a Connection Failure?

                                        -

                                        Identify a DDS DB instance connection failure caused by a client problem from the following aspects.

                                        -
                                        1. ECS Security Policy

                                          In Windows, check whether the DDS port is enabled in the Windows security policy.

                                          -

                                          In Linux, run the iptables command to check whether the DDS port is enabled in firewall settings.

                                          -
                                        2. Application Configuration

                                          Check whether the IP address, port parameter, and Java database connectivity (JDBC) are configured correctly.

                                          -
                                        -

                                        If the problem persists, contact post-sales technical support.

                                        -
                                        -
                                        -
                                        -
                                        -
                                        Parent topic: Connection and Access FAQs
                                        -
                                        -
                                        - diff --git a/docs/dds/umn/dds_faq_0015.html b/docs/dds/umn/dds_faq_0015.html index 665a36233..5af663e60 100644 --- a/docs/dds/umn/dds_faq_0015.html +++ b/docs/dds/umn/dds_faq_0015.html @@ -2,13 +2,12 @@

                                        What Should I Do If a DDS Server Problem Causes a Connection Failure?

                                        Check whether the following problems occur on the DDS database. Check the following one at a time.

                                        -
                                        1. The maximum number of connections is reached.

                                          Solution: Use the Cloud Eye resource monitoring function to check whether the number of current connections and the CPU usage are normal. If the number of connections or CPU usage reaches the maximum, restart the DDS database, disconnect DB instances, or increase the node quantity.

                                          -
                                        2. DB instance status is normal, such as a restarting or system failure.

                                          Solution: Restart the DB instance to see if the problem is resolved. If the problem persists, contact post-sales technical support.

                                          -
                                        +
                                        1. The maximum number of connections is reached.

                                          Solution: Use the Cloud Eye resource monitoring function to check whether the number of current connections and the CPU usage are normal. If the number of connections or CPU usage reaches the maximum, restart the DDS database, disconnect DB instances, or increase the node quantity.

                                          +
                                        2. Otherwise try to restart the DB instance to see if the problem is resolved. If the problem persists, contact post-sales technical support.
                                        -
                                        Parent topic: Connection and Access FAQs
                                        +
                                        Parent topic: Database Connection
                                        diff --git a/docs/dds/umn/dds_faq_0016.html b/docs/dds/umn/dds_faq_0016.html deleted file mode 100644 index 2cc0a3559..000000000 --- a/docs/dds/umn/dds_faq_0016.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                                        How Can My Applications Access a DDS DB Instance in a VPC?

                                        -

                                        Ensure that the ECS where in which your applications are located is in the same VPC and subnet as the DDS DB instance. If the ECS and the DDS DB instance are in different subnets or VPCs, modify the VPC route table and network access control list (ACL) to ensure the ECS can access the DDS DB instance.

                                        -
                                        -
                                        -
                                        -
                                        Parent topic: Connection and Access FAQs
                                        -
                                        -
                                        - diff --git a/docs/dds/umn/dds_faq_0017.html b/docs/dds/umn/dds_faq_0017.html deleted file mode 100644 index 4e6e16e56..000000000 --- a/docs/dds/umn/dds_faq_0017.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                                        Do Applications Need to Support Automatic Reconnecting to the DDS Database?

                                        -

                                        It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the database to increase service availability and continuity.

                                        -

                                        In addition, you are advised to set your applications to connect to the database using a long connection to reduce resource consumption and improve performance.

                                        -
                                        -
                                        -
                                        -
                                        Parent topic: Connection and Access FAQs
                                        -
                                        -
                                        - diff --git a/docs/dds/umn/dds_faq_0018.html b/docs/dds/umn/dds_faq_0018.html index 5ee2f4538..50b1a285d 100644 --- a/docs/dds/umn/dds_faq_0018.html +++ b/docs/dds/umn/dds_faq_0018.html @@ -3,21 +3,21 @@

                                        How Can I Install a MongoDB Client?

                                        MongoDB official website provides client installation packages for different OSs. Download the official binary installation package at https://www.mongodb.com/download-center#community.

                                        The following uses Red Hat Linux 7 and MongoDB 3.4.0 as examples to describe how to obtain the required installation package and install the MongoDB client.

                                        -

                                        Procedure

                                        1. Obtain the installation package.

                                          1. Log in at https://www.mongodb.com/download-center#community.
                                          2. Choose Server, select RHEL 7.0 Linux 64-bit x64 for OS, and click All version binaries. Figure 1 shows an example.
                                            Figure 1 MongoDB official webpage
                                            -
                                          3. Open the downloading page, click linux/mongodb-linux-x86_64-rhel70-3.4.0.tgz to download the binary installation package of MongoDB 3.4.0.
                                            Figure 2 Downloading page
                                            +

                                            Procedure

                                            1. Obtain the installation package.

                                              1. Log in at https://www.mongodb.com/download-center/community.
                                              2. Choose Server, select RHEL 7.0 Linux 64-bit x64 for OS, and click All version binaries. Figure 1 shows an example.
                                                Figure 1 MongoDB official webpage
                                                +
                                              3. Open the downloading page, click linux/mongodb-linux-x86_64-rhel70-3.4.0.tgz to download the binary installation package of MongoDB 3.4.0. Figure 2 shows an example.
                                                Figure 2 Downloading page
                                              -

                                            2. Upload the installation package to the ECS. For details about how to log in to an ECS, see How Can I Create and Log In to an ECS?
                                            3. Decompress the installation package on the ECS.

                                              tar zxvf mongodb-linux-x86_64-rhel70-3.4.0.tgz

                                              +

                                            4. Upload the installation package to the ECS. For details about how to log in to an ECS.
                                            5. Decompress the installation package on the ECS.

                                              tar zxvf mongodb-linux-x86_64-rhel70-3.4.0.tgz

                                            6. Obtain the client tool from the bin directory of the installation package.

                                              cd mongodb-linux-x86_64-rhel70-3.4.0/bin

                                              The common tools are as follows:

                                              • MongoDB client mongo
                                              • Data export tool mongoexport
                                              • Data import tool mongoimport

                                            7. Before using a client tool, assign the execute permission to it.

                                              • Run the chmod +x mongo command to grant a client permission to connect to a DB instance.
                                              • Run the chmod +x mongoexport command to grant a client permission to export data.
                                              • Run the chmod +x mongoimport command to grant a client permission to import data.
                                              -

                                            8. Connect to a DB instance through the installed client.

                                              +

                                            9. Connect to a DB instance through the installed client.

                                        -
                                        Parent topic: Connection and Access FAQs
                                        +
                                        Parent topic: Database Connection
                                        diff --git a/docs/dds/umn/dds_faq_0019.html b/docs/dds/umn/dds_faq_0019.html index 606bd7851..8f418e60b 100644 --- a/docs/dds/umn/dds_faq_0019.html +++ b/docs/dds/umn/dds_faq_0019.html @@ -13,7 +13,7 @@
                                        -
                                        Parent topic: Parameter and Metric FAQs
                                        +
                                        Parent topic: Resource Monitoring
                                        diff --git a/docs/dds/umn/dds_faq_0021.html b/docs/dds/umn/dds_faq_0021.html index dac731fce..97eac33ff 100644 --- a/docs/dds/umn/dds_faq_0021.html +++ b/docs/dds/umn/dds_faq_0021.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Network and Security FAQs
                                      +
                                      Parent topic: Network Security
                                      diff --git a/docs/dds/umn/dds_faq_0022.html b/docs/dds/umn/dds_faq_0022.html deleted file mode 100644 index 929de2074..000000000 --- a/docs/dds/umn/dds_faq_0022.html +++ /dev/null @@ -1,13 +0,0 @@ - - -

                                      Do I Need to Use DDS in a VPC?

                                      -

                                      A VPC allows you to create virtual network environment in a private and isolated network to control the private IP address range, subnets, route tables, and network gateways. The VPC also allows you to define the virtual network topology and network configuration to make the network similar to the traditional IP network you are operating in the data center.

                                      -

                                      You may need to use DDS in the VPC in the following cases:

                                      -

                                      You want to run Internet-oriented web applications and retain the backend server that the public cannot access. To do so, you can create an ECS and a DDS DB instance in the same VPC, allocate a public IP address for the ECS, and deploy a web server on the ECS.

                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Network and Security FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0023.html b/docs/dds/umn/dds_faq_0023.html index 275cbeaf0..ccf6db7fd 100644 --- a/docs/dds/umn/dds_faq_0023.html +++ b/docs/dds/umn/dds_faq_0023.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Network and Security FAQs
                                      +
                                      Parent topic: Network Security
                                      diff --git a/docs/dds/umn/dds_faq_0025.html b/docs/dds/umn/dds_faq_0025.html index 16b32cf92..452f3ac35 100644 --- a/docs/dds/umn/dds_faq_0025.html +++ b/docs/dds/umn/dds_faq_0025.html @@ -1,11 +1,11 @@ -

                                      How Do I Back Up DDS to ECS?

                                      -

                                      You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. You are advised to use the DDS backup function to store backups to a professional storage object, such as the OBS, to ensure high data reliability and service assurance.

                                      +

                                      How Do I Back Up DDS Databases to an ECS?

                                      +

                                      You can store DDS backup data on the ECS using mongoexport. However, you are advised not to store database backups on ECSs. To ensure high data reliability and service assurance, you can use the DDS backup function to store backups to a professional storage object, such as OBS.

                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Backup and Restoration
                                      diff --git a/docs/dds/umn/dds_faq_0026.html b/docs/dds/umn/dds_faq_0026.html index 1356881e7..dfa49a7f8 100644 --- a/docs/dds/umn/dds_faq_0026.html +++ b/docs/dds/umn/dds_faq_0026.html @@ -5,7 +5,7 @@
                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Backup and Restoration
                                      diff --git a/docs/dds/umn/dds_faq_0028.html b/docs/dds/umn/dds_faq_0028.html index c8f09c974..2285c9204 100644 --- a/docs/dds/umn/dds_faq_0028.html +++ b/docs/dds/umn/dds_faq_0028.html @@ -2,11 +2,11 @@

                                      What Is the DDS DB Instance Storage Configuration?

                                      The EVS is used for data storage of DDS DB instances. For details on the EVS, see Elastic Volume Service User Guide.

                                      -

                                      The DDS DB instance backup data is stored in the OBS and does not occupy the storage space you purchased. For details on the DDS DB instance storage configuration, see the Object Storage Service User Guide.

                                      +

                                      The DDS DB instance backup data is stored in the OBS and does not occupy the storage space you have. For details on the DDS DB instance storage configuration, see the Object Storage Service User Guide.

                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Database Storage
                                      diff --git a/docs/dds/umn/dds_faq_0029.html b/docs/dds/umn/dds_faq_0029.html index 8c1ae0de4..d30fb6940 100644 --- a/docs/dds/umn/dds_faq_0029.html +++ b/docs/dds/umn/dds_faq_0029.html @@ -6,7 +6,7 @@
                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Database Storage
                                      diff --git a/docs/dds/umn/dds_faq_0030.html b/docs/dds/umn/dds_faq_0030.html index 9b713d1ef..e46e8d384 100644 --- a/docs/dds/umn/dds_faq_0030.html +++ b/docs/dds/umn/dds_faq_0030.html @@ -1,11 +1,12 @@ -

                                      Which Items Occupy the Storage Space on My Purchased DDS DB Instances?

                                      -

                                      Both your common data (excluding backup data) and data required for ensuring DB instance proper running occupy the storage space on your purchased DDS DB instances. To ensure DB instance proper running, system database data, rollback logs, and indexes are required. Logs generated by DDS also occupy the DB instance storage space. These files ensure that DB instances run stably.

                                      +

                                      Which Items Occupy the Storage Space of DDS DB Instances?

                                      +

                                      The following types of data will occupy the storage space:

                                      +
                                      • User data except backups
                                      • Data required for ensuring DB instance proper running occupy, such as system database data, rollback logs, and indexes
                                      • Log output files that are generated by DDS ensure the stable operating of DDS DB instances. For example, Oplogs occupy 10% of storage space and cannot be resized.
                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Database Storage
                                      diff --git a/docs/dds/umn/dds_faq_0031.html b/docs/dds/umn/dds_faq_0031.html index fd76339b5..9b83db25c 100644 --- a/docs/dds/umn/dds_faq_0031.html +++ b/docs/dds/umn/dds_faq_0031.html @@ -1,11 +1,11 @@

                                      What Overhead Does the Storage Space Have After I Applied for a DDS DB Instance?

                                      -

                                      The storage space you applied for will contain the system overhead required for inode, reserved block, and database operation.

                                      +

                                      The storage space you applied for will contain the system overhead required for inode, reserved block, and database operation.

                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Database Storage
                                      diff --git a/docs/dds/umn/dds_faq_0032.html b/docs/dds/umn/dds_faq_0032.html index 88c9f2bc2..5b25482ba 100644 --- a/docs/dds/umn/dds_faq_0032.html +++ b/docs/dds/umn/dds_faq_0032.html @@ -26,7 +26,7 @@
                                      -
                                      Parent topic: Storage FAQs
                                      +
                                      Parent topic: Log Management
                                      diff --git a/docs/dds/umn/dds_faq_0033.html b/docs/dds/umn/dds_faq_0033.html deleted file mode 100644 index 80f5316f8..000000000 --- a/docs/dds/umn/dds_faq_0033.html +++ /dev/null @@ -1,244 +0,0 @@ - - -

                                      Which Commands are Supported or Restricted by DDS?

                                      -

                                      The following tables list the commands supported and restricted by DDS.

                                      - -

                                      Released On

                                      Description

                                      +

                                      Description

                                      2020-10-15

                                      +

                                      2022-10-30

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2019-11-07

                                      +

                                      2022-06-16

                                      +

                                      Modified the following content:

                                      + +

                                      2022-05-10

                                      +

                                      Added the description of database password.

                                      +

                                      2022-04-14

                                      +

                                      Added the following content:

                                      +

                                      Method 2

                                      +

                                      Modified the following content:

                                      + +

                                      2022-03-29

                                      +

                                      Modified the following content:

                                      + +

                                      2022-03-22

                                      +

                                      Added the following content:

                                      +

                                      Replica Set Instance

                                      +

                                      Modified the following content:

                                      + +

                                      2021-07-15

                                      +

                                      Added the following content:

                                      + +

                                      2021-06-22

                                      +

                                      Modified the following content:

                                      + +

                                      2021-04-13

                                      +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      + +

                                      2021-03-29

                                      +

                                      Modified the following content:

                                      +

                                      Supported Cross-CIDR Access in section Creating a Replica Set Instance.

                                      +

                                      2021-03-24

                                      +

                                      Added the following content:

                                      +

                                      Configuring Cross-CIDR Access for Replica Set Instances

                                      +

                                      2020-10-15

                                      +

                                      Modified the following content:

                                      + +

                                      2019-11-07

                                      		 -

                                      Modified the following content:

                                      -

                                      Supported DB instances that are compatible with MongoDB 3.4 Community Edition in sections Database Engine and Version, Creating a Cluster Instance, Creating a Replica Set Instance, and How Can I Install a MongoDB Client?

                                      +

                                      Modified the following content:

                                      +

                                      Supported DB instances that are compatible with MongoDB 3.4 Community Edition in sections Database Engine and Version, Creating a Cluster Instance, Creating a Replica Set Instance, and How Can I Install a MongoDB Client?

                                      2019-09-16

                                      +

                                      2019-09-16

                                      Modified the following content:

                                      -
                                      • Added the description of disabling OBS Browser certificate verification and the procedure for enabling the certificate verification in section Downloading Backup Files.
                                      +

                                      Modified the following content:

                                      +
                                      • Added the description of disabling OBS Browser certificate verification and the procedure for enabling the certificate verification in section Downloading Backup Files.

                                      2019-08-19

                                      +

                                      2019-08-19

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2019-07-24

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2019-07-17

                                      +

                                      2019-07-17

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2019-07-03

                                      +

                                      2019-07-03

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      + +

                                      2019-03-12

                                      +

                                      2019-03-12

                                      Accepted in OTC-4.0/Agile.

                                      +

                                      Accepted in OTC-4.0/Agile.

                                      2019-02-15

                                      +

                                      2019-02-15

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2019-01-31

                                      +

                                      2019-01-31

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2018-12-29

                                      +

                                      2018-12-29

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2018-10-08

                                      +

                                      2018-10-08

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2018-09-10

                                      +

                                      2018-09-10

                                      Modified the following content:

                                      -
                                      • Deleted the release numbers and retained the release dates only in accordance with the unified public cloud style.
                                      • Modified the description about the parameter group quotas in section Creating a Parameter Group.
                                      +

                                      Modified the following content:

                                      +
                                      • Deleted the release numbers and retained the release dates only in accordance with the unified public cloud style.
                                      • Modified the description about the parameter group quotas in section Creating a Parameter Template.

                                      2018-08-31

                                      +

                                      2018-08-31

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2018-08-17

                                      +

                                      2018-08-17

                                      Modified the following content:

                                      -
                                      • Modified the description of high-availability replica sets in section Replica Set Architecture.
                                      • Modified the description about the parameter group quotas in section Creating a Parameter Group.
                                      • Optimized the description of the step following the successful creation of a DB instance in sections Creating a Cluster Instance and Creating a Replica Set Instance.
                                      • Changed HA Type to DB Instance Type displayed on the page for creating a DB instance, optimized the buttons of the warning dialog box of restart and delete operations, and synchronized the changes to the document.
                                      +

                                      Modified the following content:

                                      +
                                      • Modified the description of high-availability replica sets in section Replica Set.
                                      • Modified the description about the parameter group quotas in section Creating a Manual Backup.
                                      • Optimized the description of the step following the successful creation of a DB instance in sections Creating a Cluster Instance and Creating a Replica Set Instance.
                                      • Changed HA Type to DB Instance Type displayed on the page for creating a DB instance, optimized the buttons of the warning dialog box of restart and delete operations, and synchronized the changes to the document.

                                      2018-08-03

                                      +

                                      2018-08-03

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2018-07-03

                                      +

                                      2018-07-03

                                      Accepted in OTC-3.1.

                                      +

                                      Accepted in OTC-3.1.

                                      2018-06-27

                                      +

                                      2018-06-27

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2018-06-21

                                      +

                                      2018-06-21

                                      Modified the following content:

                                      -
                                      • Modified the procedure for creating a DB instance and fixed the storage space of config at 20 GB in section Creating a Cluster Instance.
                                      • Supported the enabling or disabling the automated backup policy in section Setting Automated Backup Policy.
                                      • Moved the subsection "Monitoring" in chapter "Managing DDS DB Instances" to a new section Monitoring.
                                      +

                                      Modified the following content:

                                      +

                                      2018-06-04

                                      +

                                      2018-06-04

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2018-05-04

                                      +

                                      2018-05-04

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2018-03-09

                                      +

                                      2018-03-09

                                      Modified the following content:

                                      -
                                      • Modified the description of DDS and changed its location in section What Is DDS?
                                      • Added the tag editing function in section Tag.
                                      +

                                      Modified the following content:

                                      +
                                      • Modified the description of DDS and changed its location in section What Is DDS?
                                      • Added the tag editing function in section Tag Management.

                                      2018-02-23

                                      +

                                      2018-02-23

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      -
                                      • Added the description in section Setting Automated Backup Policy: If you set the retention period to one or more days, the backup policy is enabled and a full automated backup is triggered instantly.
                                      +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +
                                      • Added the description in section Setting Automated Backup Policy: If you set the retention period to one or more days, the backup policy is enabled and a full automated backup is triggered instantly.

                                      2018-02-19

                                      +

                                      2018-02-19

                                      Accepted in OTC-3.0.

                                      +

                                      Accepted in OTC-3.0.

                                      2018-02-09

                                      +

                                      2018-02-09

                                      Modified the following content:

                                      - +

                                      Modified the following content:

                                      +

                                      2018-02-02

                                      +

                                      2018-02-02

                                      Added the following content:

                                      - -

                                      Modified the following content:

                                      - +

                                      Added the following content:

                                      + +

                                      Modified the following content:

                                      +

                                      2018-01-30

                                      +

                                      2018-01-30

                                      This issue is the first official release.

                                      +

                                      This issue is the first official release.
                                      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                      Table 1 Commands supported and restricted by DDS

                                      Type

                                      -

                                      Supported Command

                                      -

                                      Restricted Command

                                      -

                                      Aggregates Commands

                                      -

                                      aggregate

                                      -

                                      count

                                      -

                                      distinct

                                      -

                                      group

                                      -

                                      mapReduce

                                      -

                                      Geospatial Commands

                                      -

                                      geoNear

                                      -

                                      geoSearch

                                      -

                                      Query and Write Operation Commands

                                      -

                                      find

                                      -

                                      insert

                                      -

                                      update

                                      -

                                      delete

                                      -

                                      findAndModify

                                      -

                                      getMore

                                      -

                                      getLastError

                                      -

                                      resetError

                                      -

                                      getPrevError

                                      -

                                      eval

                                      -

                                      parallelCollectionScan

                                      -

                                      Query Plan Cache Commands

                                      -

                                      planCacheListFilters

                                      -

                                      planCacheSetFilter

                                      -

                                      planCacheClearFilters

                                      -

                                      planCacheListQueryShapes

                                      -

                                      planCacheListPlans

                                      -

                                      planCacheClear

                                      -

                                      -

                                      -

                                      Authentication Commands

                                      -

                                      logout

                                      -

                                      authenticate

                                      -

                                      getnonce

                                      -

                                      authSchemaUpgrade

                                      -

                                      copydbgetnonce

                                      -

                                      User Management Commands

                                      -

                                      createUser

                                      -

                                      updateUser

                                      -

                                      dropUser

                                      -

                                      dropAllUsersFromDatabase

                                      -

                                      grantRolesToUser

                                      -

                                      revokeRolesFromUser

                                      -

                                      usersInfo

                                      -

                                      -

                                      -

                                      Role Management Commands

                                      -

                                      invalidateUserCache

                                      -

                                      createRole

                                      -

                                      updateRole

                                      -

                                      dropRole

                                      -

                                      dropAllRolesFromDatabase

                                      -

                                      grantPrivilegesToRole

                                      -

                                      revokePrivilegesFromRole

                                      -

                                      grantRolesToRole

                                      -

                                      revokeRolesFromRole

                                      -

                                      rolesInfo

                                      -

                                      -

                                      -

                                      Replication Commands

                                      -

                                      isMaster

                                      -

                                      replSetElect

                                      -

                                      replSetUpdatePosition

                                      -

                                      appendOplogNote

                                      -

                                      replSetFreeze

                                      -

                                      replSetGetStatus

                                      -

                                      replSetInitiate

                                      -

                                      replSetMaintenance

                                      -

                                      replSetReconfig

                                      -

                                      replSetStepDown

                                      -

                                      replSetSyncFrom

                                      -

                                      resync

                                      -

                                      applyOps

                                      -

                                      replSetGetConfig

                                      -

                                      Sharding Commands

                                      -

                                      enableSharding

                                      -

                                      getShardVersion

                                      -

                                      mergeChunks

                                      -

                                      shardCollection

                                      -

                                      split

                                      -

                                      splitChunk

                                      -

                                      splitVector

                                      -

                                      moveChunk

                                      -

                                      movePrimary

                                      -

                                      isdbgrid

                                      -

                                      flushRouterConfig

                                      -

                                      addShard

                                      -

                                      cleanupOrphaned

                                      -

                                      checkShardingIndex

                                      -

                                      listShards

                                      -

                                      removeShard

                                      -

                                      getShardMap

                                      -

                                      setShardVersion

                                      -

                                      shardingState

                                      -

                                      unsetSharding

                                      -

                                      Administration Commands

                                      -

                                      renameCollection

                                      -

                                      dropDatabase

                                      -

                                      listCollections

                                      -

                                      drop

                                      -

                                      create

                                      -

                                      convertToCapped

                                      -

                                      filemd5

                                      -

                                      createIndexes

                                      -

                                      listIndexes

                                      -

                                      dropIndexes

                                      -

                                      fsync

                                      -

                                      connectionStatus

                                      -

                                      collMod

                                      -

                                      reIndex

                                      -

                                      getParameter

                                      -

                                      currentOp

                                      -

                                      killOp

                                      -

                                      clone

                                      -

                                      cloneCollection

                                      -

                                      clean

                                      -

                                      connPoolSync

                                      -

                                      compact

                                      -

                                      setParameter

                                      -

                                      repairDatabase

                                      -

                                      repairCursor

                                      -

                                      touch

                                      -

                                      shutdown

                                      -

                                      cloneCollectionAsCapped

                                      -

                                      copydb

                                      -

                                      logRotate

                                      -

                                      Diagnostic Commands

                                      -

                                      availableQueryOptions

                                      -

                                      buildInfo

                                      -

                                      collStats

                                      -

                                      dataSize

                                      -

                                      dbStats

                                      -

                                      explain

                                      -

                                      features

                                      -

                                      listCommands

                                      -

                                      listDatabases

                                      -

                                      ping

                                      -

                                      serverStatus

                                      -

                                      whatsmyuri

                                      -

                                      connPoolStats

                                      -

                                      cursorInfo

                                      -

                                      dbHash

                                      -

                                      diagLogging

                                      -

                                      driverOIDTest

                                      -

                                      getCmdLineOpts

                                      -

                                      getLog

                                      -

                                      hostInfo

                                      -

                                      isSelf

                                      -

                                      netstat

                                      -

                                      profile

                                      -

                                      shardConnPoolStats

                                      -

                                      top

                                      -

                                      validate

                                      -

                                      Internal Commands

                                      -

                                      -

                                      -

                                      handshake

                                      -

                                      _recvChunkAbort

                                      -

                                      _recvChunkCommit

                                      -

                                      _recvChunkStart

                                      -

                                      _recvChunkStatus

                                      -

                                      _replSetFresh

                                      -

                                      mapreduce.shardedfinish

                                      -

                                      _transferMods

                                      -

                                      replSetHeartbeat

                                      -

                                      replSetGetRBID

                                      -

                                      _migrateClone

                                      -

                                      replSetElect

                                      -

                                      writeBacksQueued

                                      -

                                      writebacklisten

                                      -

                                      System Events Auditing Commands

                                      -

                                      -

                                      -

                                      logApplicationMessage

                                      -
                                      -
                                      - -
                                      -
                                      -
                                      Parent topic: FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0034.html b/docs/dds/umn/dds_faq_0034.html deleted file mode 100644 index 69fcdc07e..000000000 --- a/docs/dds/umn/dds_faq_0034.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                                      How Can I Create and Log In to an ECS?

                                      -

                                      For details on how to create and log in to an ECS, 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.

                                      -
                                      • The ECS to be created must be in the same VPC with the DDS DB instance to which it connects.
                                      • When you create an ECS, select an OS, such as Red Hat 6.6, and bind an EIP to it.
                                      • Configure the security group to enable the ECS to access the DB instance through the private IP address, that is, the value of Private IP Address of mongos on the Basic Information page.
                                      -
                                      -
                                      -
                                      -
                                      Parent topic: Connection and Access FAQs
                                      -
                                      -
                                      - diff --git a/docs/dds/umn/dds_faq_0039.html b/docs/dds/umn/dds_faq_0039.html new file mode 100644 index 000000000..d037fcec9 --- /dev/null +++ b/docs/dds/umn/dds_faq_0039.html @@ -0,0 +1,17 @@ + + +

                                      How Do I Install Robo 3T?

                                      +

                                      This section describes how to obtain the Robo 3T installation package and install Robo 3T.

                                      +

                                      Procedure

                                      1. Download Robo 3T from https://robomongo.org/download.

                                        Figure 1 Downloading page
                                        +

                                      2. In the displayed dialog box, download robo3t-1.3.1-windows-x86_64-7419c406.exe.

                                        Figure 2 Downloading Robo 3T
                                        +

                                      3. Double-click the robo3t-1.3.1-windows-x86_64-7419c406.exe file to start the installation.
                                      4. After the installation is complete, start the tool.

                                        Figure 3 Main window
                                        +

                                      5. Connect to a DB instance.

                                        +

                                      +
                                      +
                                      +
                                      +
                                      +
                                      Parent topic: Database Connection
                                      +
                                      +
                                      + diff --git a/docs/dds/umn/dds_faq_0100.html b/docs/dds/umn/dds_faq_0100.html index f34474566..ec29ac45d 100644 --- a/docs/dds/umn/dds_faq_0100.html +++ b/docs/dds/umn/dds_faq_0100.html @@ -4,19 +4,25 @@
                                      diff --git a/docs/dds/umn/dds_faq_0101.html b/docs/dds/umn/dds_faq_0101.html index ca6d74fcf..8a23336ce 100644 --- a/docs/dds/umn/dds_faq_0101.html +++ b/docs/dds/umn/dds_faq_0101.html @@ -1,15 +1,17 @@ -

                                      Common FAQs

                                      -
                                      + +

                                      Product Consulting

                                      + +

                                      +
                                      +
                                      diff --git a/docs/dds/umn/dds_faq_0102.html b/docs/dds/umn/dds_faq_0102.html index db5eb3fb7..c6bdc9b94 100644 --- a/docs/dds/umn/dds_faq_0102.html +++ b/docs/dds/umn/dds_faq_0102.html @@ -1,22 +1,13 @@ -

                                      Management FAQs

                                      -

                                      -
                                      +

                                      Database Performance

                                      +
                                      diff --git a/docs/dds/umn/dds_faq_0103.html b/docs/dds/umn/dds_faq_0103.html new file mode 100644 index 000000000..e028583fc --- /dev/null +++ b/docs/dds/umn/dds_faq_0103.html @@ -0,0 +1,17 @@ + + +

                                      Creation and Deletion

                                      +
                                      + + diff --git a/docs/dds/umn/dds_faq_0104.html b/docs/dds/umn/dds_faq_0104.html index 832b7f76f..ea6f7d443 100644 --- a/docs/dds/umn/dds_faq_0104.html +++ b/docs/dds/umn/dds_faq_0104.html @@ -1,28 +1,19 @@ -

                                      Connection and Access FAQs

                                      -

                                      -
                                      +

                                      Database Connection

                                      +
                                      diff --git a/docs/dds/umn/dds_faq_0105.html b/docs/dds/umn/dds_faq_0105.html new file mode 100644 index 000000000..9b0bc4372 --- /dev/null +++ b/docs/dds/umn/dds_faq_0105.html @@ -0,0 +1,19 @@ + + + +

                                      Database Usage

                                      + +

                                      +
                                      + + + diff --git a/docs/dds/umn/dds_faq_0107.html b/docs/dds/umn/dds_faq_0107.html new file mode 100644 index 000000000..ad42b8048 --- /dev/null +++ b/docs/dds/umn/dds_faq_0107.html @@ -0,0 +1,22 @@ + + +

                                      Database Storage

                                      +

                                      +
                                      + + diff --git a/docs/dds/umn/dds_faq_0109.html b/docs/dds/umn/dds_faq_0109.html index c55096577..cee74707d 100644 --- a/docs/dds/umn/dds_faq_0109.html +++ b/docs/dds/umn/dds_faq_0109.html @@ -1,24 +1,17 @@ -

                                      Storage FAQs

                                      -

                                      + +

                                      Backup and Restoration

                                      + +

                                      +
                                      diff --git a/docs/dds/umn/dds_faq_0110.html b/docs/dds/umn/dds_faq_0110.html index d5ca274c9..e72870fa0 100644 --- a/docs/dds/umn/dds_faq_0110.html +++ b/docs/dds/umn/dds_faq_0110.html @@ -1,14 +1,12 @@ -

                                      Network and Security FAQs

                                      +

                                      Network Security

                                      diff --git a/docs/dds/umn/dds_faq_0108.html b/docs/dds/umn/dds_faq_0111.html similarity index 76% rename from docs/dds/umn/dds_faq_0108.html rename to docs/dds/umn/dds_faq_0111.html index eeeb13318..3671940fc 100644 --- a/docs/dds/umn/dds_faq_0108.html +++ b/docs/dds/umn/dds_faq_0111.html @@ -1,6 +1,6 @@ - + -

                                      Parameter and Metric FAQs

                                      +

                                      Resource Monitoring

                                        diff --git a/docs/dds/umn/dds_faq_0112.html b/docs/dds/umn/dds_faq_0112.html new file mode 100644 index 000000000..aa5e1a803 --- /dev/null +++ b/docs/dds/umn/dds_faq_0112.html @@ -0,0 +1,19 @@ + + + +

                                        Log Management

                                        + +

                                        +
                                        + + + diff --git a/docs/dds/umn/en-us_image_0284275232.png b/docs/dds/umn/en-us_image_0000001095974032.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275232.png rename to docs/dds/umn/en-us_image_0000001095974032.png diff --git a/docs/dds/umn/en-us_image_0000001095974034.png b/docs/dds/umn/en-us_image_0000001095974034.png new file mode 100644 index 000000000..602fca1c3 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001095974034.png differ diff --git a/docs/dds/umn/en-us_image_0000001095974038.png b/docs/dds/umn/en-us_image_0000001095974038.png new file mode 100644 index 000000000..149fbd88d Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001095974038.png differ diff --git a/docs/dds/umn/en-us_image_0000001095974050.png b/docs/dds/umn/en-us_image_0000001095974050.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001095974050.png differ diff --git a/docs/dds/umn/en-us_image_0284275046.png b/docs/dds/umn/en-us_image_0000001095974074.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275046.png rename to docs/dds/umn/en-us_image_0000001095974074.png diff --git a/docs/dds/umn/en-us_image_0284275075.png b/docs/dds/umn/en-us_image_0000001095974076.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275075.png rename to docs/dds/umn/en-us_image_0000001095974076.png diff --git a/docs/dds/umn/en-us_image_0000001095974104.png b/docs/dds/umn/en-us_image_0000001095974104.png new file mode 100644 index 000000000..670c40252 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001095974104.png differ diff --git a/docs/dds/umn/en-us_image_0000001095974106.png b/docs/dds/umn/en-us_image_0000001095974106.png new file mode 100644 index 000000000..cb13f7b52 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001095974106.png differ diff --git a/docs/dds/umn/en-us_image_0000001096133860.png b/docs/dds/umn/en-us_image_0000001096133860.png new file mode 100644 index 000000000..149fbd88d Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096133860.png differ diff --git a/docs/dds/umn/en-us_image_0284275280.png b/docs/dds/umn/en-us_image_0000001096133868.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275280.png rename to docs/dds/umn/en-us_image_0000001096133868.png diff --git a/docs/dds/umn/en-us_image_0284275219.png b/docs/dds/umn/en-us_image_0000001096133880.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275219.png rename to docs/dds/umn/en-us_image_0000001096133880.png diff --git a/docs/dds/umn/en-us_image_0284275173.png b/docs/dds/umn/en-us_image_0000001096133892.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275173.png rename to docs/dds/umn/en-us_image_0000001096133892.png diff --git a/docs/dds/umn/en-us_image_0000001096133894.png b/docs/dds/umn/en-us_image_0000001096133894.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096133894.png differ diff --git a/docs/dds/umn/en-us_image_0000001096133896.png b/docs/dds/umn/en-us_image_0000001096133896.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096133896.png differ diff --git a/docs/dds/umn/en-us_image_0000001096133902.png b/docs/dds/umn/en-us_image_0000001096133902.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096133902.png differ diff --git a/docs/dds/umn/en-us_image_0284275079.png b/docs/dds/umn/en-us_image_0000001096133908.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275079.png rename to docs/dds/umn/en-us_image_0000001096133908.png diff --git a/docs/dds/umn/en-us_image_0284274943.png b/docs/dds/umn/en-us_image_0000001096133910.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274943.png rename to docs/dds/umn/en-us_image_0000001096133910.png diff --git a/docs/dds/umn/en-us_image_0284274981.png b/docs/dds/umn/en-us_image_0000001096133912.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274981.png rename to docs/dds/umn/en-us_image_0000001096133912.png diff --git a/docs/dds/umn/en-us_image_0284275018.png b/docs/dds/umn/en-us_image_0000001096133926.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275018.png rename to docs/dds/umn/en-us_image_0000001096133926.png diff --git a/docs/dds/umn/en-us_image_0000001096133932.png b/docs/dds/umn/en-us_image_0000001096133932.png new file mode 100644 index 000000000..2480f080b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096133932.png differ diff --git a/docs/dds/umn/en-us_image_0000001096293844.png b/docs/dds/umn/en-us_image_0000001096293844.png new file mode 100644 index 000000000..602fca1c3 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096293844.png differ diff --git a/docs/dds/umn/en-us_image_0000001096293846.png b/docs/dds/umn/en-us_image_0000001096293846.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096293846.png differ diff --git a/docs/dds/umn/en-us_image_0284275172.png b/docs/dds/umn/en-us_image_0000001096293848.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275172.png rename to docs/dds/umn/en-us_image_0000001096293848.png diff --git a/docs/dds/umn/en-us_image_0284275249.png b/docs/dds/umn/en-us_image_0000001096293854.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275249.png rename to docs/dds/umn/en-us_image_0000001096293854.png diff --git a/docs/dds/umn/en-us_image_0000001096293856.png b/docs/dds/umn/en-us_image_0000001096293856.png new file mode 100644 index 000000000..90425ebcf Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096293856.png differ diff --git a/docs/dds/umn/en-us_image_0000001096293872.png b/docs/dds/umn/en-us_image_0000001096293872.png new file mode 100644 index 000000000..670c40252 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096293872.png differ diff --git a/docs/dds/umn/en-us_image_0000001096293880.png b/docs/dds/umn/en-us_image_0000001096293880.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096293880.png differ diff --git a/docs/dds/umn/en-us_image_0000001096453840.png b/docs/dds/umn/en-us_image_0000001096453840.png new file mode 100644 index 000000000..a80ad72e8 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453840.png differ diff --git a/docs/dds/umn/en-us_image_0000001096453842.png b/docs/dds/umn/en-us_image_0000001096453842.png new file mode 100644 index 000000000..a80ad72e8 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453842.png differ diff --git a/docs/dds/umn/en-us_image_0000001096453848.png b/docs/dds/umn/en-us_image_0000001096453848.png new file mode 100644 index 000000000..7e9d2d831 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453848.png differ diff --git a/docs/dds/umn/en-us_image_0000001096453856.png b/docs/dds/umn/en-us_image_0000001096453856.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453856.png differ diff --git a/docs/dds/umn/en-us_image_0284275038.png b/docs/dds/umn/en-us_image_0000001096453866.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275038.png rename to docs/dds/umn/en-us_image_0000001096453866.png diff --git a/docs/dds/umn/en-us_image_0284274973.png b/docs/dds/umn/en-us_image_0000001096453870.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274973.png rename to docs/dds/umn/en-us_image_0000001096453870.png diff --git a/docs/dds/umn/en-us_image_0000001096453876.png b/docs/dds/umn/en-us_image_0000001096453876.png new file mode 100644 index 000000000..8cea5d75f Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453876.png differ diff --git a/docs/dds/umn/en-us_image_0000001096453878.png b/docs/dds/umn/en-us_image_0000001096453878.png new file mode 100644 index 000000000..b2c33a542 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453878.png differ diff --git a/docs/dds/umn/en-us_image_0284275085.png b/docs/dds/umn/en-us_image_0000001096453886.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275085.png rename to docs/dds/umn/en-us_image_0000001096453886.png diff --git a/docs/dds/umn/en-us_image_0000001096453892.png b/docs/dds/umn/en-us_image_0000001096453892.png new file mode 100644 index 000000000..7c24340c9 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001096453892.png differ diff --git a/docs/dds/umn/en-us_image_0284275178.png b/docs/dds/umn/en-us_image_0000001096453900.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275178.png rename to docs/dds/umn/en-us_image_0000001096453900.png diff --git a/docs/dds/umn/en-us_image_0000001142773895.png b/docs/dds/umn/en-us_image_0000001142773895.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773895.png differ diff --git a/docs/dds/umn/en-us_image_0000001142773899.png b/docs/dds/umn/en-us_image_0000001142773899.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773899.png differ diff --git a/docs/dds/umn/en-us_image_0284274974.png b/docs/dds/umn/en-us_image_0000001142773901.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274974.png rename to docs/dds/umn/en-us_image_0000001142773901.png diff --git a/docs/dds/umn/en-us_image_0000001142773903.png b/docs/dds/umn/en-us_image_0000001142773903.png new file mode 100644 index 000000000..4079a9b09 Binary files /dev/null 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 new file mode 100644 index 000000000..4079a9b09 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773909.png differ diff --git a/docs/dds/umn/en-us_image_0000001142773911.png b/docs/dds/umn/en-us_image_0000001142773911.png new file mode 100644 index 000000000..753ff7895 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773911.png differ diff --git a/docs/dds/umn/en-us_image_0000001142773917.png b/docs/dds/umn/en-us_image_0000001142773917.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773917.png differ diff --git a/docs/dds/umn/en-us_image_0284275120.png b/docs/dds/umn/en-us_image_0000001142773925.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275120.png rename to docs/dds/umn/en-us_image_0000001142773925.png diff --git a/docs/dds/umn/en-us_image_0284275119.png b/docs/dds/umn/en-us_image_0000001142773933.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275119.png rename to docs/dds/umn/en-us_image_0000001142773933.png diff --git a/docs/dds/umn/en-us_image_0000001142773935.png b/docs/dds/umn/en-us_image_0000001142773935.png new file mode 100644 index 000000000..b2c33a542 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773935.png differ diff --git a/docs/dds/umn/en-us_image_0000001142773955.png b/docs/dds/umn/en-us_image_0000001142773955.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142773955.png differ diff --git a/docs/dds/umn/en-us_image_0284275185.png b/docs/dds/umn/en-us_image_0000001142773957.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275185.png rename to docs/dds/umn/en-us_image_0000001142773957.png diff --git a/docs/dds/umn/en-us_image_0271515222.png b/docs/dds/umn/en-us_image_0000001142773959.png similarity index 100% rename from docs/dds/umn/en-us_image_0271515222.png rename to docs/dds/umn/en-us_image_0000001142773959.png diff --git a/docs/dds/umn/en-us_image_0000001142893853.png b/docs/dds/umn/en-us_image_0000001142893853.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142893853.png differ diff --git a/docs/dds/umn/en-us_image_0000001142893865.png b/docs/dds/umn/en-us_image_0000001142893865.png new file mode 100644 index 000000000..90425ebcf Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142893865.png differ diff --git a/docs/dds/umn/en-us_image_0269983210.png b/docs/dds/umn/en-us_image_0000001142893879.png similarity index 100% rename from docs/dds/umn/en-us_image_0269983210.png rename to docs/dds/umn/en-us_image_0000001142893879.png diff --git a/docs/dds/umn/en-us_image_0000001142893889.png b/docs/dds/umn/en-us_image_0000001142893889.png new file mode 100644 index 000000000..6639c7385 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142893889.png differ diff --git a/docs/dds/umn/en-us_image_0284274985.png b/docs/dds/umn/en-us_image_0000001142893899.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274985.png rename to docs/dds/umn/en-us_image_0000001142893899.png diff --git a/docs/dds/umn/en-us_image_0271492125.png b/docs/dds/umn/en-us_image_0000001142893907.png similarity index 100% rename from docs/dds/umn/en-us_image_0271492125.png rename to docs/dds/umn/en-us_image_0000001142893907.png diff --git a/docs/dds/umn/en-us_image_0284275230.png b/docs/dds/umn/en-us_image_0000001142893909.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275230.png rename to docs/dds/umn/en-us_image_0000001142893909.png diff --git a/docs/dds/umn/en-us_image_0000001142893921.png b/docs/dds/umn/en-us_image_0000001142893921.png new file mode 100644 index 000000000..5d7e29ce9 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001142893921.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053799.png b/docs/dds/umn/en-us_image_0000001143053799.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053799.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053801.png b/docs/dds/umn/en-us_image_0000001143053801.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053801.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053813.png b/docs/dds/umn/en-us_image_0000001143053813.png new file mode 100644 index 000000000..7e9d2d831 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053813.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053817.png b/docs/dds/umn/en-us_image_0000001143053817.png new file mode 100644 index 000000000..6bd6ebf13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053817.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053819.png b/docs/dds/umn/en-us_image_0000001143053819.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053819.png differ diff --git a/docs/dds/umn/en-us_image_0271515223.png b/docs/dds/umn/en-us_image_0000001143053823.png similarity index 100% rename from docs/dds/umn/en-us_image_0271515223.png rename to docs/dds/umn/en-us_image_0000001143053823.png diff --git a/docs/dds/umn/en-us_image_0000001143053829.png b/docs/dds/umn/en-us_image_0000001143053829.png new file mode 100644 index 000000000..01bbfe654 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053829.png differ diff --git a/docs/dds/umn/en-us_image_0284275122.png b/docs/dds/umn/en-us_image_0000001143053837.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275122.png rename to docs/dds/umn/en-us_image_0000001143053837.png diff --git a/docs/dds/umn/en-us_image_0000001143053839.png b/docs/dds/umn/en-us_image_0000001143053839.png new file mode 100644 index 000000000..8cea5d75f Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053839.png differ diff --git a/docs/dds/umn/en-us_image_0000001143053843.png b/docs/dds/umn/en-us_image_0000001143053843.png new file mode 100644 index 000000000..670c40252 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053843.png differ diff --git a/docs/dds/umn/en-us_image_0284275307.png b/docs/dds/umn/en-us_image_0000001143053849.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275307.png rename to docs/dds/umn/en-us_image_0000001143053849.png diff --git a/docs/dds/umn/en-us_image_0000001143053853.png b/docs/dds/umn/en-us_image_0000001143053853.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053853.png differ diff --git a/docs/dds/umn/en-us_image_0284275146.png b/docs/dds/umn/en-us_image_0000001143053861.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275146.png rename to docs/dds/umn/en-us_image_0000001143053861.png diff --git a/docs/dds/umn/en-us_image_0000001143053863.png b/docs/dds/umn/en-us_image_0000001143053863.png new file mode 100644 index 000000000..3840f49be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143053863.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133809.png b/docs/dds/umn/en-us_image_0000001143133809.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133809.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133815.png b/docs/dds/umn/en-us_image_0000001143133815.png new file mode 100644 index 000000000..753ff7895 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133815.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133823.png b/docs/dds/umn/en-us_image_0000001143133823.png new file mode 100644 index 000000000..7f4e9b835 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133823.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133827.png b/docs/dds/umn/en-us_image_0000001143133827.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133827.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133833.png b/docs/dds/umn/en-us_image_0000001143133833.png new file mode 100644 index 000000000..62e9a465b Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133833.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133835.png b/docs/dds/umn/en-us_image_0000001143133835.png new file mode 100644 index 000000000..4079a9b09 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133835.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133837.png b/docs/dds/umn/en-us_image_0000001143133837.png new file mode 100644 index 000000000..851e7d6be Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133837.png differ diff --git a/docs/dds/umn/en-us_image_0000001143133839.png b/docs/dds/umn/en-us_image_0000001143133839.png new file mode 100644 index 000000000..6639c7385 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133839.png differ diff --git a/docs/dds/umn/en-us_image_0284274967.png b/docs/dds/umn/en-us_image_0000001143133849.png similarity index 100% rename from docs/dds/umn/en-us_image_0284274967.png rename to docs/dds/umn/en-us_image_0000001143133849.png diff --git a/docs/dds/umn/en-us_image_0000001143133859.png b/docs/dds/umn/en-us_image_0000001143133859.png new file mode 100644 index 000000000..ad79b27da Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001143133859.png differ diff --git a/docs/dds/umn/en-us_image_0000001193533703.png b/docs/dds/umn/en-us_image_0000001193533703.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001193533703.png differ diff --git a/docs/dds/umn/en-us_image_0000001193610755.png b/docs/dds/umn/en-us_image_0000001193610755.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001193610755.png differ diff --git a/docs/dds/umn/en-us_image_0284275286.png b/docs/dds/umn/en-us_image_0000001224411716.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275286.png rename to docs/dds/umn/en-us_image_0000001224411716.png diff --git a/docs/dds/umn/en-us_image_0000001224531664.png b/docs/dds/umn/en-us_image_0000001224531664.png new file mode 100644 index 000000000..4b159e167 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001224531664.png differ diff --git a/docs/dds/umn/en-us_image_0284275295.png b/docs/dds/umn/en-us_image_0000001236135268.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275295.png rename to docs/dds/umn/en-us_image_0000001236135268.png diff --git a/docs/dds/umn/en-us_image_0000001236447314.png b/docs/dds/umn/en-us_image_0000001236447314.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001236447314.png differ diff --git a/docs/dds/umn/en-us_image_0284275118.png b/docs/dds/umn/en-us_image_0000001268771757.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275118.png rename to docs/dds/umn/en-us_image_0000001268771757.png diff --git a/docs/dds/umn/en-us_image_0000001269051821.png b/docs/dds/umn/en-us_image_0000001269051821.png new file mode 100644 index 000000000..62f127d6e Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001269051821.png differ diff --git a/docs/dds/umn/en-us_image_0000001280327773.png b/docs/dds/umn/en-us_image_0000001280327773.png new file mode 100644 index 000000000..aa2b82d13 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001280327773.png differ diff --git a/docs/dds/umn/en-us_image_0284275123.png b/docs/dds/umn/en-us_image_0000001280455205.png similarity index 100% rename from docs/dds/umn/en-us_image_0284275123.png rename to docs/dds/umn/en-us_image_0000001280455205.png diff --git a/docs/dds/umn/en-us_image_0000001490031014.png b/docs/dds/umn/en-us_image_0000001490031014.png new file mode 100644 index 000000000..5b1e4ce70 Binary files /dev/null and b/docs/dds/umn/en-us_image_0000001490031014.png differ diff --git a/docs/dds/umn/en-us_image_0284274979.png b/docs/dds/umn/en-us_image_0284274979.png deleted file mode 100644 index 7cabd6199..000000000 Binary files a/docs/dds/umn/en-us_image_0284274979.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284274989.png b/docs/dds/umn/en-us_image_0284274989.png deleted file mode 100644 index 97358745f..000000000 Binary files a/docs/dds/umn/en-us_image_0284274989.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275009.png b/docs/dds/umn/en-us_image_0284275009.png deleted file mode 100644 index 97358745f..000000000 Binary files a/docs/dds/umn/en-us_image_0284275009.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275043.png b/docs/dds/umn/en-us_image_0284275043.png deleted file mode 100644 index 30c3d923b..000000000 Binary files a/docs/dds/umn/en-us_image_0284275043.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275089.png b/docs/dds/umn/en-us_image_0284275089.png deleted file mode 100644 index b26f87fc8..000000000 Binary files a/docs/dds/umn/en-us_image_0284275089.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275156.png b/docs/dds/umn/en-us_image_0284275156.png deleted file mode 100644 index 1909444d2..000000000 Binary files a/docs/dds/umn/en-us_image_0284275156.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275158.png b/docs/dds/umn/en-us_image_0284275158.png deleted file mode 100644 index 680a1e334..000000000 Binary files a/docs/dds/umn/en-us_image_0284275158.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275220.png b/docs/dds/umn/en-us_image_0284275220.png deleted file mode 100644 index 97358745f..000000000 Binary files a/docs/dds/umn/en-us_image_0284275220.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275243.png b/docs/dds/umn/en-us_image_0284275243.png deleted file mode 100644 index 30c3d923b..000000000 Binary files a/docs/dds/umn/en-us_image_0284275243.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275259.png b/docs/dds/umn/en-us_image_0284275259.png deleted file mode 100644 index b7fd23a5d..000000000 Binary files a/docs/dds/umn/en-us_image_0284275259.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275268.png b/docs/dds/umn/en-us_image_0284275268.png deleted file mode 100644 index 247a08a4a..000000000 Binary files a/docs/dds/umn/en-us_image_0284275268.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275296.png b/docs/dds/umn/en-us_image_0284275296.png deleted file mode 100644 index 97358745f..000000000 Binary files a/docs/dds/umn/en-us_image_0284275296.png and /dev/null differ diff --git a/docs/dds/umn/en-us_image_0284275300.png b/docs/dds/umn/en-us_image_0284275300.png deleted file mode 100644 index 97358745f..000000000 Binary files a/docs/dds/umn/en-us_image_0284275300.png and /dev/null differ diff --git a/docs/dds/umn/en-us_topic_0000001159335385.html b/docs/dds/umn/en-us_topic_0000001159335385.html new file mode 100644 index 000000000..3ef2ef07e --- /dev/null +++ b/docs/dds/umn/en-us_topic_0000001159335385.html @@ -0,0 +1,23 @@ + + +

                                        Changing the DB Instance Class

                                        +

                                        Scenarios

                                        This section describes how to change the DB instance class.

                                        +
                                        • A DB instance cannot be deleted when you are changing its instance class.
                                        • Instances can be scaled up or down.
                                        • For cluster and replica set instances, when the DB instance class is changed, a primary/secondary switchover may occur and the database connection will be interrupted for up to 30s. You are advised to change the specifications during off-peak hours to reduce impacts and ensure that your client can reconnect to the database if the connection is interrupted.
                                        • For a single node instance, services will be interrupted up to 10 minutes when you change DB instance class. You are advised to perform this operation during off-peak hours. After the restart is complete, the cached memory will be automatically cleared. The DB instance needs to be warmed up to prevent congestion during peak hours.
                                        +
                                        +
                                        +
                                        + + diff --git a/docs/dds/umn/en-us_topic_0044018333.html b/docs/dds/umn/en-us_topic_0044018333.html new file mode 100644 index 000000000..6e0932aa6 --- /dev/null +++ b/docs/dds/umn/en-us_topic_0044018333.html @@ -0,0 +1,229 @@ + + +

                                        Creating a Cluster Instance

                                        +

                                        Scenarios

                                        This section describes how to create a Community Edition cluster instance on the DDS management console. DDS allows you to tailor your compute resources and storage space to your business needs.

                                        +

                                        You can use your account to create up to 10 cluster instances. To create more cluster instances, click in the upper right corner of the management console. On the Service Quota page, click Increase Quota to apply for quotas.

                                        +
                                        +

                                        Procedure

                                        1. Log in to the DDS console.
                                        2. On the Instance Management page, click Create DB Instance.
                                        3. On the displayed page, select your DB instance specifications and click Create Now.

                                          +

                                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                          Table 1 Basic information

                                          Parameter

                                          +

                                          Description

                                          +

                                          Region

                                          +

                                          A region where the tenant is located. It can be changed in the upper left corner. For details, see section Regions and AZs.

                                          +
                                          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 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 Changing a DB Instance Name.

                                          +

                                          +

                                          +

                                          Database Type

                                          +

                                          Community Edition

                                          +

                                          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.

                                          +

                                          Compatible MongoDB Version

                                          +
                                          • 4.2
                                          • 4.0
                                          • 3.4
                                          • 3.2
                                          +

                                          Storage Type

                                          +

                                          Ultra-high I/O

                                          +

                                          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 Regions and AZs.

                                          +

                                          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 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 2 Specifications

                                          Parameter

                                          +

                                          Description

                                          +

                                          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.

                                          +

                                          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.

                                          +

                                          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.

                                          +

                                          For details, see Modifying a Parameter Template.

                                          +

                                          shard node class

                                          +

                                          For details about the shard 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.

                                          +

                                          shard storage space

                                          +

                                          The value ranges from 10 GB to 2000 GB and must be a multiple of 10. After a DB instance is created, you can scale up its storage space. For details, see section Scaling Up Storage Space.

                                          +

                                          shard nodes

                                          +

                                          The number of shard nodes. The shard node stores user data but cannot be accessed directly.

                                          +

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

                                          +

                                          shard parameter template

                                          +

                                          The parameters that apply to the shard 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.

                                          +

                                          config node class

                                          +

                                          The CPU and memory of a config node. The config node stores the DB instance configurations but cannot be accessed directly. For details, see DB Instance Specifications.

                                          +

                                          config storage space

                                          +

                                          The storage space is 20 GB and cannot be scaled up.

                                          +

                                          config parameter template

                                          +

                                          The parameters that apply to the config 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.

                                          +
                                          +
                                          + +
                                          + + + + + + + + + + + + + + + + +
                                          Table 3 Network

                                          Parameter

                                          +

                                          Description

                                          +

                                          VPC

                                          +

                                          The VPC where your DB instances are located. A VPC isolates networks for different services, so you can easily manage and configure internal networks and change network configuration. You need to create or select the required VPC. For details about how to create a VPC, see section "Creating a VPC" in the Virtual Private Cloud User Guide. For details about the constraints on the use of VPCs, see Connection Methods.

                                          +
                                          NOTE:

                                          After the DDS instance is created, the VPC cannot be changed.

                                          +
                                          +

                                          Subnet

                                          +

                                          A subnet provides dedicated network resources that are logically isolated from other networks for network security.

                                          +

                                          After the instance is created, you can change the private IP address assigned by the subnet. For details, see Changing a Private IP Address.

                                          +

                                          Security Group

                                          +

                                          A security group controls access between DDS and other services for security.

                                          +
                                          NOTE:

                                          Ensure that the security group rule you set allows clients to access DB instances. For example, select the TCP protocol with inbound direction, input the default port number 8635, and enter a subnet IP address or select a security group that the DB instance belongs to.

                                          +
                                          +

                                          SSL

                                          +

                                          Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

                                          +

                                          You can enable SSL to improve data security. After a DB instance is created, you can connect to it using SSL.

                                          +
                                          +
                                          + +
                                          + + + + + + + + + + + + + +
                                          Table 4 Database configuration

                                          Parameter

                                          +

                                          Description

                                          +

                                          Administrator

                                          +

                                          The default account is rwuser.

                                          +

                                          Administrator Password

                                          +

                                          Set a password for the administrator. The password must be 8 to 32 characters in length and contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+?

                                          +

                                          Keep this password secure. If lost, the system cannot retrieve it for you.

                                          +

                                          Confirm Password

                                          +

                                          Enter the administrator password again.

                                          +
                                          +
                                          + +
                                          + + + + + + + +
                                          Table 5 Tag

                                          Parameter

                                          +

                                          Description

                                          +

                                          Tags

                                          +

                                          This setting is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for a DB instance.

                                          +

                                          A tag is composed of a key-value pair.

                                          +
                                          • Key: Mandatory if the DB instance is going to be tagged
                                            • Each tag key must be unique for each DB instance.
                                            • A tag key consists of up to 36 characters.
                                            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
                                            +
                                          • Value: Optional if the DB instance is going to be tagged
                                            • The value consists of up to 43 characters.
                                            • The key can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).
                                            +
                                          +

                                          After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Tag Management.

                                          +
                                          +
                                          +

                                          DB instance performance is determined by how you configure it during the creation. The hardware configuration items that can be selected include the node class and storage space.

                                          +
                                          +

                                        4. On the displayed page, confirm the DB instance information.

                                          • If you need to modify the specifications, click Previous to return to the previous page.
                                          • If you do not need to modify the specifications, click Submit to start the instance creation.
                                          +

                                        5. After a DDS DB instance is created, you can view and manage it on the Instance Management page.

                                          • When a DB instance is being created, the status displayed in the Status column is Creating. This process takes about 15 minutes. After the creation is complete, the status changes to Available.
                                          • DDS enables the automated backup policy by default. After a DB instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of a DB instance.
                                          • The default DDS port is 8635, but this port can be modified if necessary. If you change the port, you need to add the security group rule to enable access.
                                          +

                                        +
                                        +
                                        + + diff --git a/docs/dds/umn/en-us_topic_0044018334.html b/docs/dds/umn/en-us_topic_0044018334.html index 89daf2ebb..b5e983a72 100644 --- a/docs/dds/umn/en-us_topic_0044018334.html +++ b/docs/dds/umn/en-us_topic_0044018334.html @@ -1,49 +1,62 @@ -

                                        Connecting to a DB Instance Through a Client

                                        -

                                        Scenarios

                                        This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt connections to ensure data security.

                                        -

                                        Based on the application scenario, you can determine whether to access a DB instance through an EIP. For details, see Scenarios.

                                        -

                                        This section uses the Linux OS as an example to describe how to connect to a cluster instance.

                                        +

                                        Connecting to a Cluster Instance Over Private Networks

                                        +

                                        Scenarios

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

                                        +

                                        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.

                                        -

                                        Restrictions

                                        For details about restrictions on connecting to a DB instance, see Restrictions.

                                        +

                                        Constraints

                                        For details about constraints on connecting to a DB instance, see Constraints and Recommendations.

                                        -

                                        Prerequisites

                                        1. An ECS or a device that can access DDS is ready for use.
                                          • To connect to a DDS DB instance from an ECS, you need to create and log in to the ECS. For details, see How Can I Create and Log In to an ECS?
                                          • To connect to a DB instance through an EIP:
                                            1. For details on how to bind an EIP, see section Binding an EIP.
                                            2. Ensure that your local device can access the EIP that has been bound to the DB instance.
                                            -
                                          -
                                        2. A MongoDB client has been installed on the prepared ECS or the device.

                                          For details on how to install a MongoDB client, see section How Can I Install a MongoDB Client?

                                          +

                                          Prerequisites

                                          1. For details on how to create and log in to an ECS, 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.
                                          2. Install the MongoDB client on the ECS.

                                            For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

                                            +

                                            If you use a connection address to connect to a cluster instance, download the MongoDB client of version later than 3.4.

                                            +
                                          -

                                          SSL Connection

                                          1. On the Instance Management page, click the target DB instance.
                                          2. In the navigation pane on the left, choose Connections.
                                          3. In the Basic Information area, click next to the SSL field to download the root certificate.
                                          4. Upload the root certificate to the ECS that connects to the DB instance or save the root certificate to a local device that can access DDS.

                                            The following describes how to upload the certificate to a Linux and Window ECS:

                                            -
                                            • In Linux, run the following command:
                                              scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
                                              • IDENTITY_FILE indicates the directory where the root certificate locates. The file access permission is 600.
                                              • REMOTE_USER indicates the ECS OS user.
                                              • REMOTE_ADDRESS indicates the ECS address.
                                              • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
                                              +

                                              Connecting to a DB Instance Using the MongoDB Client (SSL)

                                              If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

                                              +
                                              +
                                              1. On the Instance Management page, click the target DB instance.
                                              2. In the navigation pane on the left, choose Connections.
                                              3. In the Basic Information area, click next to the SSL field.

                                                The certificate can also be downloaded from the Node Information area on the Basic Information page.

                                                +
                                                +

                                              4. Upload the root certificate to the ECS to be connected to the DB instance.

                                                The following describes how to upload the certificate to a Linux and Window ECS:

                                                +
                                                • In Linux, run the following command:
                                                  scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
                                                  • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
                                                  • REMOTE_USER indicates the ECS OS user.
                                                  • REMOTE_ADDRESS indicates the ECS address.
                                                  • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
                                                  -
                                                • In Windows, upload the root certificate using file transfer tools.
                                                -

                                              5. Connect to the DB instance in the directory where the MongoDB client is located.

                                                The Linux OS is used as an example.

                                                -

                                                ./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH>

                                                -

                                                Enter the database account password when prompted:

                                                -
                                                Enter password:
                                                -
                                                • A cluster instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection through an EIP.
                                                • 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. If a device can access the DB instance through an EIP, set this parameter to the EIP displayed in EIP 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_USER indicates the database account name. The default value is rwuser.
                                                • FILE_PATH indicates the path where the root certificate is stored.
                                                +
                                              6. In Windows, upload the root certificate using the remote connection tool.
                                            +

                                          5. Connect to the DB instance in the directory where the MongoDB client is located.

                                            • Method 1: Using standard parameters

                                              mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

                                              +

                                              Enter the database account password when prompted:

                                              +
                                              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.

                                              +
                                            +
                                            • 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.
                                            -

                                            Example:

                                            -

                                            ./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt

                                            +
                                            • Connect to the instance using standard parameters. The following is an example command:

                                              mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

                                              +
                                            • Using standard URI format

                                              mongo mongodb://rwuser:<password>@192.168.1.6:8635/test?authSource=admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

                                              +

                                          6. Check the connection result. If the following information is displayed, the connection is successful.

                                            mongos>

                                          -

                                          Common Connection

                                          To use the common connection mode, you need to disable the SSL connection. For details, see section Disabling SSL.

                                          +

                                          Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

                                          If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

                                          -
                                          1. Log in to the prepared ECS or the device that can access the document database.
                                          2. Connect to the DB instance in the directory where the MongoDB client is located.

                                            ./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

                                            -

                                            Enter the database account password when prompted:

                                            -
                                            Enter password:
                                            -
                                            • 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. If a device can access the DB instance through an EIP, set this parameter to the EIP displayed in EIP 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_USER indicates the database account name. The default value is rwuser.
                                            +
                                            1. Connect to the DB instance in the directory where the MongoDB client is located.

                                              • Method 1: Using standard parameters

                                                mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

                                                +

                                                Enter the database account password when prompted:

                                                +
                                                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.

                                                +
                                              +
                                              • 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.
                                              -

                                              Example:

                                              -

                                              ./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

                                              +
                                              • Connect to the instance using standard parameters. The following is an example command:

                                                mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

                                                +
                                              • Using standard URI format:

                                                mongo mongodb://rwuser:<password>@192.168.1.6:8635/test?authSource=admin

                                                +

                                            2. Check the connection result. If the following information is displayed, the connection is successful.

                                              mongos>

                                            diff --git a/docs/dds/umn/en-us_topic_0104472218.html b/docs/dds/umn/en-us_topic_0104472218.html index 2bb4a7b92..5214307ec 100644 --- a/docs/dds/umn/en-us_topic_0104472218.html +++ b/docs/dds/umn/en-us_topic_0104472218.html @@ -1,20 +1,16 @@ -

                                            Changing the CPU or Memory of a Cluster DB Instance

                                            -

                                            Scenarios

                                            This section guides you on how to change the CPU or memory of a cluster instance.

                                            -
                                            • A DB instance cannot be deleted when you are changing its CPU or memory.
                                            • Instances can be both scaled up and down.
                                            • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU and memory. You are advised to perform this operation during off-peak hours.
                                            -
                                            -
                                            -

                                            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, modify required parameters and click Submit.
                                            5. View the DB instance CPU or memory modification 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 about 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 check whether the scaling up is successful.
                                              +

                                              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 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, modify required parameters and click Submit.
                                              5. View the DB instance CPU or memory modification 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 about 25 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 check whether the scaling up is successful.
                                                +

                                                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_0104721795.html b/docs/dds/umn/en-us_topic_0104721795.html index daea16db6..3679ff784 100644 --- a/docs/dds/umn/en-us_topic_0104721795.html +++ b/docs/dds/umn/en-us_topic_0104721795.html @@ -1,17 +1,14 @@ -

                                              Changing the CPU or Memory of a Replica Set DB Instance

                                              -

                                              Scenarios

                                              This section guides you on how to change the CPU or memory of your replica set instance.

                                              -
                                              • A DB instance cannot be deleted when you are changing its CPU or memory.
                                              • Instances can be both scaled up and down.
                                              • Services will be interrupted for 5 to 10 minutes when you change DB instance CPU and memory. You are advised to perform this operation during off-peak hours.
                                              -
                                              -
                                              -

                                              Procedure

                                              1. Log in to the DDS console.
                                              2. On the Instance Management page, locate the target replica set instance and choose Change Instance Class in the Operation column.
                                              3. On the displayed page, modify required parameters and click Submit.
                                              4. View the DB instance CPU or memory modification 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 about 25 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 replica set instance you scaled up and check whether the scaling up is successful in the DB Information area.
                                                +

                                                Changing a Replica Set DB Instance Class

                                                +

                                                Procedure

                                                1. Log in to the DDS console.
                                                2. On the Instance Management page, locate the replica set instance and choose More > Change Instance Class in the Operation column.

                                                  Alternatively, on the Instance Management page, click the name of the replica set instance. In the DB Information area on the Basic Information page, click Change to the right of the Node Class field.

                                                  +

                                                3. On the displayed page, modify required parameters and click Submit.
                                                4. 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 replica set instance you scaled up and check whether the scaling up is successful in the DB Information area.

                                                diff --git a/docs/dds/umn/en-us_topic_0105284966.html b/docs/dds/umn/en-us_topic_0105284966.html index 31bf9a285..358d5d12e 100644 --- a/docs/dds/umn/en-us_topic_0105284966.html +++ b/docs/dds/umn/en-us_topic_0105284966.html @@ -1,46 +1,53 @@ -

                                                Connecting to a DB Instance Through a Client

                                                -

                                                Scenarios

                                                This section guides you on how to connect to DB instances through a database client using a common connection or an SSL connection. You are advised to use SSL to encrypt connections to ensure data security.

                                                -

                                                Based on the application scenario, you can determine whether to access a DB instance through an EIP. For details, see Scenarios.

                                                -

                                                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.

                                                -

                                                This section uses the Linux OS as an example to describe how to connect to a replica set instance.

                                                +

                                                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.

                                                +

                                                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.

                                                -

                                                Restrictions

                                                For details about restrictions on connecting to a DB instance, see Restrictions.

                                                +

                                                Constraints

                                                For details about constraints on connecting to a replica set instance over private networks, see Constraints and Recommendations.

                                                -

                                                Prerequisites

                                                1. An ECS or a device that can access DDS is ready for use.
                                                  • To connect to a DDS DB instance from an ECS, you need to create and log in to the ECS. For details, see How Can I Create and Log In to an ECS?
                                                  • To connect to a DB instance through an EIP:
                                                    1. Bind an EIP to a DB instance node. For details, see section Binding an EIP.
                                                    2. Ensure that your local device can access the EIP that has been bound to the DB instance.
                                                    -
                                                  -
                                                2. A MongoDB client has been installed on the prepared ECS or the device.

                                                  For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

                                                  +

                                                  Prerequisites

                                                  1. For details on how to create and log in to an ECS, 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.
                                                  2. Install the MongoDB client on the ECS.

                                                    For details on how to install a MongoDB client, see How Can I Install a MongoDB Client?

                                                  -

                                                  SSL Connection

                                                  1. On the Instance Management page, click the target DB instance.
                                                  2. In the navigation pane on the left, choose Connections.
                                                  3. In the Basic Information area, click next to the SSL field to download the root certificate.
                                                  4. Upload the root certificate to the ECS that connects to the DB instance or save the root certificate to a local device that can access DDS.

                                                    The following describes how to upload the certificate to a Linux and Window ECS:

                                                    -
                                                    • In Linux, run the following command:
                                                      scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
                                                      • IDENTITY_FILE indicates the directory where the root certificate locates. The file access permission is 600.
                                                      • REMOTE_USER indicates the ECS OS user.
                                                      • REMOTE_ADDRESS indicates the ECS address.
                                                      • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
                                                      +

                                                      Connecting to a DB Instance Using the MongoDB Client (SSL)

                                                      If you connect to a DB instance using this method, enable the SSL connection. For details, see section Enabling SSL.

                                                      +
                                                      +
                                                      1. On the Instance Management page, click the target DB instance.
                                                      2. In the navigation pane on the left, choose Connections.
                                                      3. In the Basic Information area, click next to the SSL field.
                                                      4. Upload the root certificate to the ECS to be connected to the DB instance.

                                                        The following describes how to upload the certificate to a Linux and Window ECS:

                                                        +
                                                        • In Linux, run the following command:
                                                          scp <IDENTITY_FILE> <REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>
                                                          • IDENTITY_FILE indicates the directory where the root certificate resides. The file access permission is 600.
                                                          • REMOTE_USER indicates the ECS OS user.
                                                          • REMOTE_ADDRESS indicates the ECS address.
                                                          • REMOTE_DIR indicates the directory of the ECS to which the root certificate is uploaded.
                                                          -
                                                        • In Windows, upload the root certificate using file transfer tools.
                                                        -

                                                      5. Connect to a DDS DB instance.

                                                        The Linux OS is used as an example.

                                                        -

                                                        ./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

                                                        -

                                                        Enter the database account password when prompted:

                                                        -
                                                        Enter password:
                                                        -
                                                        • A replica set instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection.
                                                        • 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. If a device can access the DB instance through an EIP, set this parameter to the EIP displayed in EIP 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_USER indicates the database account name. The default value is rwuser.
                                                        • FILE_PATH indicates the path where the root certificate is stored.
                                                        +
                                                      6. In Windows, upload the root certificate using the remote connection tool.
                                                    +

                                                  5. Connect to a DDS DB instance.

                                                    • Method 1: Using standard parameters

                                                      mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

                                                      +

                                                      Enter the database account password when prompted:

                                                      +
                                                      Enter password:
                                                      +
                                                    • Method 2: Using standard URI format

                                                      mongo "mongodb://rwuser:<password>@<DB_HOST1>:<DB_PORT1>,<DB_HOST2>:<DB_PORT2>/test?authSource=admin&replicaSet=replica" --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

                                                      +

                                                      If the DB instance is connected using the connection address, add double quotation marks before and after the connection information. The connection information can be obtained in the Address column on the Instance Management page.

                                                      +
                                                    +
                                                    • A replica set instance uses the management IP address to generate SSL certificate. --sslAllowInvalidHostnames is needed for the SSL connection through a private network.
                                                    • 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.
                                                    -

                                                    Example:

                                                    -

                                                    ./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

                                                    -

                                                  6. Check the connection result. If the following information is displayed, the connection is successful.

                                                    • Result from connecting the primary node in a replica set:
                                                      replica:PRIMARY>
                                                      +
                                                      • Connect to the instance using standard parameters. The following is an example command:

                                                        mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

                                                        +
                                                      • Connect to the DB instance using standard URI format. The following is an example command:

                                                        mongo "mongodb://rwuser:<password>@192.168.1.6:8635,192.168.1.80:8635/test?authSource=admin&replicaSet=replica" --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

                                                        +
                                                      +

                                                    • Check the connection result. If the following information is displayed, the connection is successful.

                                                      • Result from connecting to the primary node in a replica set or connecting to the whole replica set:
                                                        replica:PRIMARY>
                                                      • Result from connecting the secondary node in a replica set:
                                                        replica:SECONDARY>

                                                  -

                                                  Common Connection

                                                  To use the common connection mode, you need to disable the SSL connection. For details, see section Disabling SSL.

                                                  +

                                                  Connecting to a DB Instance Using the MongoDB Client (Non-SSL)

                                                  If you connect to a DB instance using this method, disable the SSL connection. For details, see section Disabling SSL.

                                                  -
                                                  1. Log in to the prepared ECS or the device that can access the document database.
                                                  2. Connect to a DDS DB instance.

                                                    ./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

                                                    -

                                                    Enter the database account password when prompted:

                                                    -
                                                    Enter password:
                                                    -
                                                    • 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. If a device can access the DB instance through an EIP, set this parameter to the EIP displayed in EIP 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_USER indicates the database account name. The default value is rwuser.
                                                    +
                                                    1. Connect to a DDS DB instance.

                                                      • Method 1: Using standard parameters

                                                        mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

                                                        +

                                                        Enter the database account password when prompted:

                                                        +
                                                        Enter password:
                                                        +
                                                      • Method 2: Using unencrypted connection

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

                                                        +

                                                        If the DB instance is connected using the connection address, add double quotation marks before and after the connection information. The connection information can be obtained in the Address column on the Instance Management page.

                                                        +
                                                      +
                                                      • 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.
                                                      -

                                                      Example:

                                                      -

                                                      ./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

                                                      -

                                                    2. Check the connection result. If the following information is displayed, the connection is successful.

                                                      • Result from connecting the primary node in a replica set:
                                                        replica:PRIMARY>
                                                        +
                                                        • Connect to the instance using standard parameters. The following is an example command:

                                                          mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

                                                          +
                                                        • Connect to the DB instance using standard URI format. The following is an example command:

                                                          mongo "mongodb://rwuser:<password>@192.168.1.6:8635,192.168.1.80:8635/test?authSource=admin&replicaSet=replica"

                                                          +
                                                        +

                                                      • Check the connection result. If the following information is displayed, the connection is successful.

                                                        • Result from connecting to the primary node in a replica set or connecting to the whole replica set:
                                                          replica:PRIMARY>
                                                        • Result from connecting the secondary node in a replica set:
                                                          replica:SECONDARY>

                                                    @@ -48,7 +55,7 @@
                                                    diff --git a/docs/dds/umn/en-us_topic_backup_download.html b/docs/dds/umn/en-us_topic_backup_download.html index 98a061a7f..915e0001b 100644 --- a/docs/dds/umn/en-us_topic_backup_download.html +++ b/docs/dds/umn/en-us_topic_backup_download.html @@ -3,14 +3,14 @@

                                                    Downloading Backup Files

                                                    Scenarios

                                                    This section describes how to download manual or automated backup files for local data backup or restoration.

                                                    -

                                                    Procedure

                                                    1. Log in to the DDS console.
                                                    2. In the navigation pane on the left, click Backup Management.
                                                    3. On the Backup Management page, click the Clusters or Replica Sets tab, locate the available backup you want to download and click Download in the Operation column.
                                                    4. Download OBS Browser and install it.
                                                    5. Log in to the OBS Browser.

                                                      For details on how to log in to OBS Browser, see section Logging In to OBS Browser in the Object Storage Service User Guide.

                                                      -

                                                    6. Disable certificate verification on OBS Browser.

                                                      For details on how to configure OBS Browser, see section Configuring the System in the Object Storage Service User Guide.

                                                      -

                                                      The OBS bucket names displayed on the Download Backup File page on the DDS console do not support certificate verification. Therefore, you need to disable OBS Browser certificate verification before adding external buckets and enable it after the backup files are downloaded.

                                                      +

                                                      Procedure

                                                      1. Log in to the DDS console.
                                                      2. In the navigation pane on the left, click Backup Management.
                                                      3. On the Backup Management page, click the Clusters, Replica Sets, or Single Nodes tab, locate the target backup you want to download and click Download in the Operation column.
                                                      4. Download OBS Browser and install it.
                                                      5. Log in to the OBS Browser.

                                                        For details on how to log in to OBS Browser, see section Logging In to OBS Browser in the Object Storage Service User Guide.

                                                        +

                                                      6. Disable certificate verification on OBS Browser.

                                                        For details on how to configure OBS Browser, see section Configuring the System in the Object Storage Service User Guide.

                                                        +

                                                        The OBS bucket names displayed on the Download Backup File page on the DDS console do not support certificate verification. Therefore, you need to disable OBS Browser certificate verification before adding external buckets and enable it after the backup files are downloaded.

                                                      7. Add an external bucket.

                                                        In the Create Bucket dialog box of OBS Browser, select Add external bucket and enter the bucket name displayed on Download Backup File of the DDS console.

                                                        For details about how to add external buckets, see section Adding External Buckets in the Object Storage Service User Guide.

                                                      8. Download the backup files.

                                                        In the search box on the right of OBS Browser, enter the backup file name displayed on Download Backup File of the DDS console.

                                                        -

                                                      9. After the backup file is downloaded, enable OBS Browser certificate verification.
                                                      +

                                                    7. Enable OBS Browser certificate verification after the backup files are downloaded.
                                                    diff --git a/docs/dds/umn/en-us_topic_backup_restore.html b/docs/dds/umn/en-us_topic_backup_restore.html index 3f218e99a..d0dc5e254 100644 --- a/docs/dds/umn/en-us_topic_backup_restore.html +++ b/docs/dds/umn/en-us_topic_backup_restore.html @@ -1,24 +1,22 @@

                                                    Setting Automated Backup Policy

                                                    -

                                                    Scenarios

                                                    DDS backs up data automatically based on the automated backup policy you set. You are advised to regularly back up data in your database. If the database becomes faulty or data is damaged, you can restore it with the backup, ensuring data reliability.

                                                    -
                                                    • DDS checks existing automated backup files. If the retention period of a file exceeds the backup retention period you set, DDS will delete the file.
                                                    • After the backup policy is modified, an automated backup will be triggered based on the new backup policy. The retention period of the previously generated automated backups remains unchanged.
                                                    -
                                                    +

                                                    DDS backs up data automatically based on the automated backup policy you set. You are advised to regularly back up data in your database. If the database becomes faulty or data is damaged, you can restore it with the backup.

                                                    +

                                                    The automated backup policy for DDS is enabled by default. After an instance is created, you can modify or disable the automated backup policy as required.

                                                    +

                                                    The default automated backup policy is as follows:

                                                    +
                                                    • Retention period: 7 days
                                                    • Time window: The default time window is a one hour time interval within 24 hours, for example, 01:00-02:00. The backup time is in UTC format.
                                                    • Backup cycle: Each day of the week.
                                                    +

                                                    Once the automated backup policy is enabled, a full backup is triggered immediately. After that, full backups will be created based on the backup window and backup cycle you specify. When an instance is being backed up, data is copied and then compressed and uploaded to OBS. The length of time the backup data is kept for depends on the backup retention period you configure. The backup duration depends on the amount of data, and the average backup speed is 60 MB/s. After the automated backup policy is enabled, an incremental backup is automatically performed every 5 minutes to ensure data reliability.

                                                    +

                                                    Precautions

                                                    • The backup process does not affect services.
                                                    • DDS checks existing automated backup files. If the retention period of a file exceeds the backup retention period you set, DDS will delete the file.
                                                    • After the backup policy is modified, an automated backup will be triggered based on the new backup policy. The retention period of the previously generated automated backups remains unchanged.
                                                    -
                                                    • Backup files are stored in OBS buckets.
                                                    • When a DB instance is created, DDS enables the automated backup policy by default. The default settings of the parameters are as follows. You can modify them after a DB instance is created.
                                                      • Backups are retained for 7 days by default.
                                                      • The time window is in UTC by default.
                                                      • Data is backed up every day by default.
                                                      -
                                                    -

                                                    Enabling or Modifying an Automated Backup Policy

                                                    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 Backups & Restorations.
                                                    4. On the Backups & Restorations page, click Modify Backup Policy. If you want to enable the automated backup policy, click .

                                                      Retention period refers to the number of days that data is kept. You can increase the retention period to improve data reliability.

                                                      +

                                                      Enabling or Modifying an Automated Backup Policy

                                                      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 Backups & Restorations.
                                                      4. On the Backups & Restorations page, click Modify Backup Policy. If you want to enable the automated backup policy, click .

                                                        Retention Period refers to the number of days that data is kept. You can increase the retention period to improve data reliability.

                                                        The backup retention period can range from 1 to 732 days, with a time window of one hour. The backup cycle varies according to the retention period you have set.

                                                        • If you set the retention period to 1 to 6 days, data is automatically backed up each day of the week.
                                                        • If you set the retention period to 7 to 732 days, you must select at least one day of the week for the backup cycle.
                                                        -

                                                      5. Click OK to save the modification.
                                                      6. View the backup result.

                                                        • If the automated backup policy is enabled, an automated full backup is immediately triggered. The time it takes to complete the backup depends on the size of the job.
                                                        • If the automated backup policy is modified, an automated full backup is randomly triggered during the time window you set. The time it takes to complete the backup depends on the size of the job.
                                                        • During the creation of an automated backup, you can query the backup status on the Backup Management page or the Backups & Restorations tab. The backup status is Backing up.
                                                        • In the upper right corner of the backup list, click to refresh the list. The backup status changes to Complete. The backup type is Automated and the backup method is Physical.
                                                        +

                                                      7. Click OK to save the modification.
                                                      8. View the backup result.

                                                        • If the automated backup policy is enabled, an automated full backup is immediately triggered. The time it takes to complete the backup depends on the size of the job.
                                                        • If the automated backup policy is modified, an automated full backup is randomly triggered during the time window you set. The time it takes to complete the backup depends on the size of the job.
                                                        • During the creation of an automated backup, you can check the backup status on the Backup Management page or the Backups & Restorations tab. The backup status is Backing up.
                                                        • In the upper right corner of the backup list, click to refresh the list. The backup status changes to Completed. The backup type is Automated.

                                                      -

                                                      Disabling an Automated Backup Policy

                                                      Observe the following constraints when disabling the automated backup policy:

                                                      -
                                                      • Your data cannot be backed up.
                                                      • If you choose to delete all the existing automated backup when disabling the automated backup policy, related restoration or download operations will fail.
                                                      -
                                                      -
                                                      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 Backups & Restorations.
                                                      4. On the Backups & Restorations page, click Modify Backup Policy. On the displayed page, click to disable the automated backup policy.

                                                        You can determine whether to delete all automated backup files:

                                                        +

                                                        Disabling an Automated Backup Policy

                                                        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 Backups & Restorations.
                                                        4. On the Backups & Restorations page, click Modify Backup Policy. On the displayed dialog box, click to disable the automated backup policy.

                                                          You can determine whether to delete all automated backup files:

                                                          • If you do not select Delete automated backups, all backup files within the retention period will be retained. You can manually delete them. For details, see section Deleting an Automated Backup.
                                                          • If you select Delete automated backups, all backup files within the retention period will be deleted.
                                                          -

                                                        5. Click OK.
                                                        +

                                                      5. Click OK.
                                                    diff --git a/docs/dds/umn/en-us_topic_change_database_port.html b/docs/dds/umn/en-us_topic_change_database_port.html deleted file mode 100644 index 6d7d62550..000000000 --- a/docs/dds/umn/en-us_topic_change_database_port.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

                                                    Changing the Database Port

                                                    -

                                                    Scenarios

                                                    This section guides you on how to modify the database port to ensure system security. The database port cannot be changed when the instance is in any of the following statuses:

                                                    -
                                                    • Restarting
                                                    • Adding nodes
                                                    • Switching SSL
                                                    • Changing instance class
                                                    • Deleting node
                                                    -
                                                    -

                                                    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, choose Connections.
                                                    4. In the Basic Information area, click to right of the Database Port field to modify the database port.

                                                      The database port range is 2100 to 9500.

                                                      -
                                                      • If you want to submit the change, click . This process takes about 1 to 5 minutes.
                                                      • If you want to cancel the change, click .
                                                      -

                                                    5. View the modification result.
                                                    -
                                                    -
                                                    -
                                                    -
                                                    -
                                                    Parent topic: Security
                                                    -
                                                    -
                                                    - diff --git a/docs/dds/umn/en-us_topic_change_security_group.html b/docs/dds/umn/en-us_topic_change_security_group.html deleted file mode 100644 index 2c59905cd..000000000 --- a/docs/dds/umn/en-us_topic_change_security_group.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

                                                    Changing a Security Group

                                                    -

                                                    Scenarios

                                                    This section guides you on how to change the security group of a DB instance. If any of the following operations is in progress, do not change the security group:

                                                    -
                                                    • Adding nodes
                                                    • Migrating data
                                                    -
                                                    -

                                                    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, choose Connections.
                                                    4. In the Security Group area, click to select the security group to which the DB instance belongs.

                                                      • If you want to submit the change, click . This process takes about 1 to 3 minutes.
                                                      • If you want to cancel the change, click .
                                                      -

                                                    5. View the modification result.
                                                    -
                                                    -
                                                    -
                                                    -
                                                    -
                                                    Parent topic: Security
                                                    -
                                                    -
                                                    - diff --git a/docs/dds/umn/en-us_topic_configuration.html b/docs/dds/umn/en-us_topic_configuration.html index 155b71263..ed7c12c5c 100644 --- a/docs/dds/umn/en-us_topic_configuration.html +++ b/docs/dds/umn/en-us_topic_configuration.html @@ -1,23 +1,33 @@ -

                                                    Editing a Parameter Group

                                                    -

                                                    Scenarios

                                                    This section guides you on how to edit parameters in the parameter groups that you have created to meet your service requirements and achieve optimal performance.

                                                    +

                                                    Modifying a Parameter Template

                                                    +

                                                    You can modify parameters in custom parameter templates as needed to get the most out of DDS performance.

                                                    +

                                                    You can modify parameters in either of the following ways:

                                                    +
                                                    • Directly modify the parameters of a specified instance.

                                                      If you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately regardless of the Effective upon Reboot setting. If you modify static parameters on the Parameters page of an instance and save the modifications, the modifications take effect only after you manually restart the target instance.

                                                      +
                                                    • Modify the parameters in a parameter template and apply the template to the instance.

                                                      The changes only take effect after you apply the template to the instance. If you modify static parameters in a custom parameter template on the Parameter Template Management page and save the modifications, the modifications take effect only after you apply the parameter template to instances and manually restart the instances. For operation details, see Applying a Parameter Template.

                                                      +
                                                    +

                                                    Precautions

                                                    • You can change parameter values in custom parameter templates but cannot change the default parameter templates provided by the system. You can only click the name of a default parameter template to view its details.
                                                    • If a custom parameter template is set incorrectly, the instance associated with the template may fail to start. You can re-configure the custom parameter template according to the configurations of the default parameter template.
                                                    +
                                                    +

                                                    Modifying Parameters of an Instance

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                                    4. In the navigation pane on the left, choose Instance Management. On the displayed page, click the DB instance whose parameters you wish to modify.
                                                    5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

                                                      • To save the modifications, click Save.
                                                      • If you want to cancel the modifications, click Cancel.
                                                      • If you want to preview the modifications, click Preview.
                                                      +
                                                      +

                                                    6. After parameters are modified, click Change History to view parameter modification details.

                                                      For details about how to view parameter modification details, see Viewing Parameter Change History.

                                                      After you modify instance parameters, the modifications immediately take effect for the instance.

                                                      +
                                                      Check the value in the Effective upon Restart column.
                                                      • If the value is Yes and the instance status on the Instance Management page is Pending restart, restart the DB instance for the modifications to take effect.
                                                      • If the value is No, the modifications take effect immediately.
                                                      -

                                                      Default parameter groups are unchangeable. You can only view them by clicking their names. If inappropriate settings of user-created parameter groups lead to a database reboot failure, you can refer to the settings of the default parameter groups to reset them.

                                                      -

                                                      Procedure

                                                      1. Log in to the DDS console.
                                                      2. In the navigation pane on the left, click Parameter Group Management.
                                                      3. On the Parameter Group Management page, select the Clusters or Replica Sets tab and click the parameter group you created.
                                                      4. Modify the required parameters.

                                                        Related parameters are described as follows:

                                                        -
                                                        • For details on parameter descriptions, visit MongoDB official website.
                                                        • The default value of the net.maxIncomingConnections parameter varies according to DB instance specifications. Therefore, this parameter is set to default before being specified.
                                                        -

                                                        Possible operations are as follows:

                                                        -
                                                        • If you want to save the modifications, click Save.
                                                        • If you want to cancel the modifications, click Cancel.
                                                        • If you want to preview the modifications, click Preview.
                                                        -

                                                        For details on the description of parameter group status, see section Database Status.

                                                        -

                                                        After modifying a parameter, you need to view the associated instance status in the instance list. If Pending restart is displayed, you need to restart the instance for the modification to take effect.

                                                        +
                                                        +

                                                      +
                                                      +

                                                      Modifying Parameters in a Custom Parameter Template

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                                      4. In the navigation pane on the left, click Parameter Template Management.
                                                      5. On the Parameter Template Management page, click Custom Templates. Select the Clusters, Replica Sets, or Single Nodes sub-tab and click the parameter template you created.
                                                      6. Modify the required parameters.

                                                        • If you want to save the modifications, click Save.
                                                        • If you want to cancel the modifications, click Cancel.
                                                        • If you want to preview the modifications, click Preview.
                                                        +
                                                        +

                                                      7. After parameters are modified, click Change History to view parameter modification details.

                                                        For details about how to view parameter modification details, see Viewing Parameter Change History.
                                                        • The modifications take effect only after you apply the parameter template to instances. For details, see Applying a Parameter Template.
                                                        • The change history page displays only the modifications of the last seven days.
                                                        • For details about the parameter template statuses, see DB Instance Status.
                                                        • After modifying a parameter, view the associated instance status in the instance list. If Pending restart is displayed, restart the instance for the modification to take effect. For details, see Restarting a DB Instance or a Node.
                                                        +

                                                      -
                                                      Parent topic: Parameter Group
                                                      +
                                                      Parent topic: Parameter Template Management
                                                      diff --git a/docs/dds/umn/en-us_topic_error_log.html b/docs/dds/umn/en-us_topic_error_log.html index 6db787b4d..091146357 100644 --- a/docs/dds/umn/en-us_topic_error_log.html +++ b/docs/dds/umn/en-us_topic_error_log.html @@ -1,15 +1,15 @@

                                                      Error Log

                                                      -

                                                      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.

                                                        • Log records of different node types of a cluster instance in batches
                                                          • If you select All nodes, the logs of all nodes in the cluster instance are displayed.
                                                          • If you select All mongos, the logs of all mongos in the cluster instance are displayed.
                                                          • If you select All shards, the logs of all shards in the cluster instance are displayed.
                                                          • If you select All configs, the logs of all configs in the cluster instance are displayed.
                                                          -
                                                        • Log records of all nodes of a replica set instance
                                                        • Log records of a node in different time periods
                                                        • Time, levels, and descriptions of the logs
                                                        +

                                                        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.

                                                        -
                                                        Parent topic: Monitoring
                                                        +
                                                        Parent topic: Log Management
                                                        diff --git a/docs/dds/umn/en-us_topic_increase_nodes.html b/docs/dds/umn/en-us_topic_increase_nodes.html index 4297ebe32..48feddd79 100644 --- a/docs/dds/umn/en-us_topic_increase_nodes.html +++ b/docs/dds/umn/en-us_topic_increase_nodes.html @@ -1,22 +1,22 @@ -

                                                        Adding Cluster Instance Nodes

                                                        -

                                                        Scenarios

                                                        This section guides you on how to add nodes to a DB instance.

                                                        +

                                                        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 one or more nodes are being added.
                                                        +
                                                        • 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.
                                                        -

                                                        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, mongos Quantity, and Parameter Group. Then, click Submit.

                                                          A cluster instance of Community Edition supports a maximum of 16 mongos nodes.

                                                          -

                                                        5. View the result of adding nodes.

                                                          • This process takes about 10 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 Cluster Instance Nodes.
                                                          +

                                                          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 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. On the displayed page, specify Node Class, Storage Space, shard Quantity, and Parameter Group. Then, click Submit.

                                                            • The storage space you applied for will contain the system overhead required for inode, reserved block, and database operation. The storage space must be an integer multiple of 10.
                                                            • A cluster instance of Community Edition supports a maximum of 16 shard nodes.
                                                            -

                                                          5. View the result of adding nodes.

                                                            • This process takes about 10 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 shard tab in the Node Information area, view the information about the node you added.
                                                            • If the shards fail to be added, you can revert them in batches or delete them one by one. For details, see section Reverting 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.
                                                              +

                                                            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 shard tab in the Node Information area, view the information about the node you added.
                                                              • If the shards 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.

                                                          -
                                                          Parent topic: Storage
                                                          +
                                                          Parent topic: Instance Management
                                                          diff --git a/docs/dds/umn/en-us_topic_increase_storage.html b/docs/dds/umn/en-us_topic_increase_storage.html index 52f6fd845..30a4a62e0 100644 --- a/docs/dds/umn/en-us_topic_increase_storage.html +++ b/docs/dds/umn/en-us_topic_increase_storage.html @@ -1,22 +1,28 @@

                                                          Scaling Up Storage Space

                                                          -

                                                          Scenarios

                                                          This section guides you on how to scale up the storage space of a DB instance to suit your service requirements.

                                                          +

                                                          Scenarios

                                                          This section describes how to scale up the storage space of a DB instance to suit your service requirements.

                                                          -
                                                          • You can scale up a DB instance a maximum of eight times.
                                                          • You cannot scale up a DB instance in Creating, Changing instance class, Adding node, or Deleting node status.
                                                          • You cannot scale down storage space.
                                                          • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
                                                          • You cannot scale up the storage space of a config for the cluster instances.
                                                          +
                                                          • You can scale up a DB instance a maximum of eight times.
                                                          • You cannot scale up a DB instance in Creating, Changing instance class, Adding node, or Deleting node status.
                                                          • Storage space can only be scaled up. It cannot be scaled down.
                                                          • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
                                                          • You cannot scale up the storage space of a config for the cluster instances.
                                                          • During the scale-up process, the DB instance will not restart, and your services will not be interrupted.
                                                          -

                                                          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 shard tab, locate the target shard, and click Scale Storage Space in the Operation column.
                                                          4. On the displayed page, specify the desired storage space, and click Submit.

                                                            You must add a minimum of 10 GB each time you scale up, and only multiples of 10 GB are allowed. The maximum amount of storage space is 1,000 GB.

                                                            -

                                                          5. Check the scaling-up result.

                                                            • This process takes about 3 to 5 minutes. The status of the DB instance in the instance list is Scaling up.
                                                            • 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 shard tab and check whether the scaling up is successful.
                                                            +

                                                            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 shard tab, locate the target shard, and click Scale Storage Space in the Operation column.
                                                            4. On the displayed page, specify the desired storage space, and click Submit.

                                                              You must add a minimum of 10 GB each time you scale up, and only multiples of 10 GB are allowed. The maximum amount of storage space is 2000 GB.

                                                              +

                                                            5. Check the scale-up result.

                                                              • This process takes up to 5 minutes. The status of the DB instance in the instance list is Scaling up.
                                                              • 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 shard tab and check whether the scale up was successful.

                                                            -

                                                            Replica Set

                                                            1. Log in to the DDS console.
                                                            2. On the Instance Management page, locate the target replica set instance and click Scale Storage Space in the Operation column.
                                                            3. On the displayed page, specify the desired storage space, and click Submit.

                                                              You must add a minimum of 10 GB each time you scale up, and only multiples of 10 GB are allowed. The maximum amount of storage space is 2,000 GB.

                                                              -

                                                            4. Check the scaling-up result.

                                                              • This process takes about 3 to 5 minutes. The status of the DB instance in the instance list is Scaling up.
                                                              • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
                                                              • In the Storage Space area on the Basic Information page, check whether the scaling up is successful.
                                                              +

                                                              Replica Set

                                                              1. Log in to the DDS console.
                                                              2. On the Instance Management page, locate the target replica set instance and click Scale Storage Space in the Operation column.

                                                                Alternatively, you can click the target cluster instance, in the Storage Space area on the Basic Information page, click on the Scale button.

                                                                +

                                                              3. On the displayed page, specify the desired storage space, and click Submit.

                                                                You must add a minimum of 10 GB each time you scale up, and only multiples of 10 GB are allowed. The maximum amount of storage space is 3000 GB.

                                                                +

                                                              4. Check the scale-up result.

                                                                • This process takes up to 5 minutes. The status of the DB instance in the instance list is Scaling up.
                                                                • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
                                                                • In the Storage Space area on the Basic Information page, check whether the scaling up is successful.
                                                                +

                                                              +
                                                              +

                                                              Single Node

                                                              1. Log in to the DDS console.
                                                              2. On the Instance Management page, locate the target single node instance and click Scale Storage Space in the Operation column.

                                                                Alternatively, you can click the target cluster instance, in the Storage Space area on the Basic Information page, click on the Scale button.

                                                                +

                                                              3. On the displayed page, specify the desired storage space and click Submit.

                                                                You must add a minimum of 10 GB each time you scale up, and only multiples of 10 GB are allowed. The maximum amount of storage space is 1000 GB.

                                                                +

                                                              4. Check the scale-up result.

                                                                • This process takes up to 5 minutes. The status of the DB instance in the instance list is Scaling up.
                                                                • In the upper right corner of the DB instance list, click to refresh the list. The instance status changes to Available.
                                                                • In the Storage Space area on the Basic Information page, check whether the scaling up is successful.

                                                            -
                                                            Parent topic: Storage
                                                            +
                                                            Parent topic: Instance Management
                                                            diff --git a/docs/dds/umn/en-us_topic_introduction.html b/docs/dds/umn/en-us_topic_introduction.html index c143527dd..00ddf3869 100644 --- a/docs/dds/umn/en-us_topic_introduction.html +++ b/docs/dds/umn/en-us_topic_introduction.html @@ -1,10 +1,10 @@

                                                            What Is DDS?

                                                            -

                                                            Document Database Service (DDS) is compatible with MongoDB and is secure, highly available, reliable, scalable, and easy to use. It provides DB instance creation, scaling, redundancy, backup, restoration, monitoring, and alarm reporting functions with just a few clicks on the DDS console.

                                                            -

                                                            DDS has the following characteristics:

                                                            -
                                                            • Automatically sets up three-node replica set architecture. DDS supports fast deployment, high availability (HA) data storage, data redundancy, and failover support.
                                                            • Provides sharded cluster instances consisting of shard, mongos, and config, enabling you to easily enhance read and write performance and build a distributed DDS database system.
                                                            • Provides database backup and restoration functions on the DDS console.
                                                            • Provides performance metrics and sets alarms on any of the metrics to send you notification. You can quickly monitor instance status and identify issues at a glance.
                                                            -

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

                                                            +

                                                            Document Database Service (DDS) is a high availability DBaaS, which provides a secure, reliable and scalable solution, compatible with MongoDB. 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.
                                                            +

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

                                                            diff --git a/docs/dds/umn/en-us_topic_parameter_group.html b/docs/dds/umn/en-us_topic_parameter_group.html index 986807ad1..a609997b3 100644 --- a/docs/dds/umn/en-us_topic_parameter_group.html +++ b/docs/dds/umn/en-us_topic_parameter_group.html @@ -1,20 +1,22 @@ -

                                                            Creating a Parameter Group

                                                            -

                                                            Scenarios

                                                            DB parameter groups act as a container for engine configuration values that are applied to one or more DB instances. This section guides you on how to create a parameter group to manage your DB instance configurations.

                                                            +

                                                            Creating a Parameter Template

                                                            +

                                                            DB parameter templates act as a container for engine configuration values that are applied to one or more DB instances.

                                                            +

                                                            Precautions

                                                            • DDS does not share parameter template quotas with RDS.
                                                            • Each account can create up to 100 DDS parameter templates for the cluster, replica set, and single node instances.
                                                            -
                                                            • DDS does not share parameter group quotas with RDS.
                                                            • Each account can create up to 100 DDS parameter groups for the cluster and replica set instances to share.
                                                            -
                                                            -

                                                            Cluster

                                                            1. Log in to the DDS console.
                                                            2. In the navigation pane on the left, click Parameter Group Management.
                                                            3. On the Parameter Group Management page, click Create Parameter Group.
                                                            4. Select a DB engine version from the DB Engine Version drop-down list, Cluster for DB Instance Type, specify Node Type, Parameter Group Name, and Description, and then click OK.

                                                              • Node Type: specifies the node type that this parameter group will apply to. For example, to create a parameter group applying to config, select config.
                                                              • Parameter Group Name: specifies the parameter group name, which is a string of 1 to 64 characters composed of only letters (case-sensitive), digits, hyphens (-), underscores (_), and periods (.).
                                                              • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                                                              -

                                                            5. On the Parameter Group Management page, view and manage parameter groups on the Clusters tab.
                                                            +

                                                            Cluster

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                                            4. In the navigation pane on the left, choose Parameter Template Management.
                                                            5. On the Parameter Template Management page, click Create Parameter Template.
                                                            6. Select Cluster for DB Instance Type, specify DB Engine Version, Node Type, New Parameter Template, and Description (optional), and then click OK.

                                                              • Node Type: specifies the node type that this parameter template will apply to. For example, to create a parameter template applying to config, select config.
                                                              • New Parameter Template: The template name can be 4 to 64 characters long and starts with a letter. It can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
                                                              • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                                                              +

                                                            7. On the Parameter Template Management page, view and manage parameter templates on the Clusters tab.
                                                            -

                                                            Replica Set

                                                            1. Log in to the DDS console.
                                                            2. In the navigation pane on the left, click Parameter Group Management.
                                                            3. On the Parameter Group Management page, click Create Parameter Group.
                                                            4. Select a DB engine version from the DB Engine Version drop-down list, Replica set for DB Instance Type, specify Parameter Group Name and Description, and then click OK.

                                                              • Parameter Group Name: specifies the parameter group name, which is a string of 1 to 64 characters composed of only letters (case-sensitive), digits, hyphens (-), underscores (_), and periods (.).
                                                              • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                                                              -

                                                            5. On the Parameter Group Management page, view and manage parameter groups on the Replica Sets tab.
                                                            +

                                                            Replica Set

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                                            4. In the navigation pane on the left, choose Parameter Template Management.
                                                            5. On the Parameter Template Management page, click Create Parameter Template.
                                                            6. Select Replica set for DB Instance Type, specify DB Engine Version, New Parameter Template, and Description (optional), and then click OK.

                                                              • New Parameter Template: The template name can be 4 to 64 characters long and starts with a letter. It can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
                                                              • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                                                              +

                                                            7. On the Parameter Template Management page, view and manage parameter templates on the Replica Sets tab.
                                                            +
                                                            +

                                                            Single Node

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Document Database Service to go to the DDS console.
                                                            4. In the navigation pane on the left, choose Parameter Template Management.
                                                            5. On the Parameter Template Management page, click Create Parameter Template .
                                                            6. Select Single node for DB Instance Type, specify DB Engine Version, New Parameter Template, and Description (optional), and then click OK.

                                                              • New Parameter Template: The template name can be 4 to 64 characters long and starts with a letter. It can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
                                                              • Description: contains a maximum of 256 characters and cannot contain the carriage return character and the following special characters: >!<"&'=
                                                              +

                                                            7. On the Parameter Template Management page, view and manage parameter templates on the Single Nodes tab.
                                                            -
                                                            Parent topic: Parameter Group
                                                            +
                                                            Parent topic: Parameter Template Management
                                                            diff --git a/docs/dds/umn/en-us_topic_reset_password.html b/docs/dds/umn/en-us_topic_reset_password.html deleted file mode 100644 index 1dfc78d51..000000000 --- a/docs/dds/umn/en-us_topic_reset_password.html +++ /dev/null @@ -1,19 +0,0 @@ - - -

                                                            Resetting the Administrator Password

                                                            -

                                                            Scenarios

                                                            You are advised to change administrator passwords periodically to prevent password cracking, ensuring system security. You cannot reset the administrator password under the following circumstances:

                                                            -
                                                            -
                                                            • Restarting
                                                            • Adding node
                                                            • Switching SSL
                                                            • Changing port
                                                            • Changing instance class
                                                            • Deleting node
                                                            -

                                                            Method 1

                                                            1. Log in to the DDS console.
                                                            2. On the Instance Management page, locate the target DB instance and choose More > Reset Password in the Operation column.
                                                            3. Enter and confirm the new administrator password and click OK.

                                                              The password is a string of 8 to 32 characters. It must be a combination of uppercase letters, lowercase letters, digits, and special characters. You can also use the following special characters: ~!@#%^*-_=+?

                                                              -

                                                            -
                                                            -

                                                            Method 2

                                                            1. Log in to the DDS console.
                                                            2. On the Instance Management page, click the target DB instance.
                                                            3. In the DB Information area on the Basic Information page, click Reset Password to the right of the Administrator field.
                                                            4. Enter and confirm the new administrator password and click OK.

                                                              The password is a string of 8 to 32 characters. It must be a combination of uppercase letters, lowercase letters, digits, and special characters. You can also use the following special characters: ~!@#%^*-_=+?

                                                              -

                                                            -
                                                            -
                                                            -
                                                            -
                                                            -
                                                            Parent topic: Security
                                                            -
                                                            -
                                                            - diff --git a/docs/dds/umn/en-us_topic_slow_query_log.html b/docs/dds/umn/en-us_topic_slow_query_log.html index f9a0b3c67..018635e91 100644 --- a/docs/dds/umn/en-us_topic_slow_query_log.html +++ b/docs/dds/umn/en-us_topic_slow_query_log.html @@ -1,15 +1,18 @@

                                                            Slow Query Log

                                                            -

                                                            Slow query logs record statements whose execution period exceeds the value of slowms (100 ms by default), allowing you identify and optimize slowly executed statements.

                                                            -

                                                            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 Slow Query Logs.
                                                            4. On the displayed page, click Slow Query Logs. Then, view the log details.

                                                              • Log records of all shards of a cluster instance
                                                              • Log records of all nodes of a replica set instance
                                                              • Log records of a node in different time periods
                                                              • Statements of the following level
                                                                • All statement type
                                                                • INSERT
                                                                • QUERY
                                                                • UPDATE
                                                                • REMOVE
                                                                • GETMORE
                                                                • COMMAND
                                                                -
                                                              +

                                                              Scenarios

                                                              Slow query logs record statements whose execution period exceeds the value of operationProfiling.slowOpThresholdMs (100 ms by default). With slow query logs, you can identify and optimize slowly executed statements.

                                                              +

                                                              If the user would like to change this, they can do this in Section Modifying a Parameter Template.

                                                              +
                                                              +
                                                              +

                                                              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 Slow Query Logs.
                                                              4. On the Slow Query Logs page, set search criteria and click Search to view log information.

                                                                • Log records of all shards or a shard-specific node of a cluster instance
                                                                • Log records of all nodes of a replica set instance
                                                                • Slow query statements of the following level
                                                                  • All statements
                                                                  • INSERT
                                                                  • QUERY
                                                                  • UPDATE
                                                                  • REMOVE
                                                                  • GETMORE
                                                                  • COMMAND
                                                                  +
                                                                • You can view up to 2,000 slow query logs of a specified node type, of a specified statement type, and within a specified period.

                                                              -
                                                              Parent topic: Monitoring
                                                              +
                                                              Parent topic: Log Management
                                                              diff --git a/docs/dds/umn/en-us_topic_user_guide.html b/docs/dds/umn/en-us_topic_user_guide.html index b88a7fbbd..a7906bb9d 100644 --- a/docs/dds/umn/en-us_topic_user_guide.html +++ b/docs/dds/umn/en-us_topic_user_guide.html @@ -10,16 +10,20 @@
                                                            5. Basic Concepts
                                                              6. -
                                                            6. Product Advantages
                                                              -
                                                              7. -
                                                            7. DDS DB Instance
                                                              +
                                                            8. Functions and Features
                                                            9. Typical Application Scenarios
                                                              10. -
                                                            10. Related Services
                                                              +
                                                            11. DDS DB Instance
                                                              +
                                                              12. +
                                                            12. Constraints and Recommendations
                                                            13. User Permissions
                                                              14. +
                                                            14. Permissions Management
                                                              +
                                                              15. +
                                                            15. Related Services
                                                              +
                                      diff --git a/docs/dds/umn/public_sys-resources/delta.gif b/docs/dds/umn/public_sys-resources/delta.gif index f1371e584..0d1b1f674 100644 Binary files a/docs/dds/umn/public_sys-resources/delta.gif and b/docs/dds/umn/public_sys-resources/delta.gif differ diff --git a/docs/dds/umn/public_sys-resources/deltaend.gif b/docs/dds/umn/public_sys-resources/deltaend.gif index c79293760..cc7da0fc8 100644 Binary files a/docs/dds/umn/public_sys-resources/deltaend.gif and b/docs/dds/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-arrowdn.gif b/docs/dds/umn/public_sys-resources/icon-arrowdn.gif index 84eec9be2..379428032 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-arrowdn.gif and b/docs/dds/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-arrowrt.gif b/docs/dds/umn/public_sys-resources/icon-arrowrt.gif index 39583d168..6aaaa11c2 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-arrowrt.gif and b/docs/dds/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-caution.gif b/docs/dds/umn/public_sys-resources/icon-caution.gif index 6e90d7cfc..079c79b26 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-caution.gif and b/docs/dds/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-danger.gif b/docs/dds/umn/public_sys-resources/icon-danger.gif index 6e90d7cfc..079c79b26 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-danger.gif and b/docs/dds/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-note.gif b/docs/dds/umn/public_sys-resources/icon-note.gif index 6314297e4..31be2b039 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-note.gif and b/docs/dds/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-notice.gif b/docs/dds/umn/public_sys-resources/icon-notice.gif index 3f4e40cec..409070650 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-notice.gif and b/docs/dds/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-tip.gif b/docs/dds/umn/public_sys-resources/icon-tip.gif index 93aa72053..c47bae05c 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-tip.gif and b/docs/dds/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/dds/umn/public_sys-resources/icon-warning.gif b/docs/dds/umn/public_sys-resources/icon-warning.gif index 6e90d7cfc..079c79b26 100644 Binary files a/docs/dds/umn/public_sys-resources/icon-warning.gif and b/docs/dds/umn/public_sys-resources/icon-warning.gif differ