Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
- What's New
- Function Overview
- Service Overview
-
Getting Started
- Overview
- Getting Started with Clusters
- Getting Started with Replica Sets
- Getting Started with Single Nodes
- Logging In to the DDS Console
- Example: Buying and Connecting to a DDS Instance
- Change History (Getting Started) Europe Site
-
User Guide
- Migrating Data
- Performance Tuning
- Permissions Management
- Instance Lifecycle Management
- Instance Modifications
- Data Backups
- Data Restorations
-
Parameter Template Management
- Overview
- Creating a Parameter Template
- Modifying a Parameter Template
- Viewing Parameter Change History
- Exporting a Parameter Template
- Comparing Parameter Templates
- Replicating a Parameter Template
- Resetting a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Connection Management
- Database Usage
- Data Security
- Monitoring and Alarm Reporting
- Auditing
- Logs
- Task Center
- Billing
- Tags
- Quotas
- DDS Usage Suggestions
- Change History
- Developer Guide
-
Best Practices
- Overview
- Common Methods for Connecting to a DDS Instance
- How Do Replica Sets Achieve High Availability and Read/Write Splitting?
- Sharding
- How Do I Improve DDS Performance by Optimizing SQL Statements?
- How Do I Prevent the Mongos Cache Problem?
- How Do I Solve the High CPU Usage Issue?
- Creating a User and Granting the Read-Only Permission to the User
- Security White Paper
- Performance White Paper
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
APIs V3.0 (Recommended)
- Querying the API Version
- Querying Database Version Information
- Querying Database Specifications
- Querying the Database Disk Type
-
DB Instance Management
- Creating a DB Instance
- Restarting a DB Instance
- Deleting a DB Instance
- Querying Instances and Details
- Scaling Up Storage Space
- Adding Nodes for a Cluster Instance
- Modifying DB Instance Specifications
- Performing a Primary/Secondary Switchover in a Replica Set Instance
- Enabling or Disabling SSL
- Modifying a DB Instance Name
- Changing an Instance Description
- Changing a Database Port
- Changing a Security Group
- Binding an EIP
- Unbinding an EIP
- Changing a Private IP Address
- Creating Shard or Config IP Addresses of a Cluster Instance
- Configuring Cross-CIDR Access for a Replica Set
- Querying AZs to Which an Instance Can Be Migrated
- Migrating a DB Instance to Another AZ
- Adding Nodes to a Replica Set Instance
- Adding a Read Replica to an Instance
- Connection Management
-
Backup and Restoration
- Creating a Manual Backup
- Deleting a Manual Backup
- Querying the Backup List
- Querying an Automated Backup Policy
- Setting an Automated Backup Policy
- Restoring Data to a New DB Instance
- Obtaining the Link for Downloading a Backup File
- Querying the Restoration Time Ranges
- Obtaining the List of Databases That Can Be Restored
- Obtaining the List of Database Collections That Can Be Restored
- Restoring Data to the Original DB Instance
- Restoring Databases and Tables to a Point in Time
- Parameter Configuration
- Log Information Queries
- Tag Management
-
Managing Databases and Users
- Creating a Database User
- Creating a Database Role
- Querying Details About Database Users
- Querying the Database Role List
- Changing the Password of a Database User
- Checking the Password for Logging In to a Database
- Querying Cluster Balancing Settings
- Enabling or Disabling Cluster Balancing
- Setting the Activity Time Window for Cluster Balancing
- Deleting a Database User
- Deleting a Database Role
- Quota Management
- Task Management
- API V3 (Unavailable Soon)
- Examples
- Permissions Policies and Supported Actions
- Appendix
- Change History (European Sites)
- SDK Reference
-
FAQs
-
Product Consulting
- What Is the Relationship Between DDS and MongoDB Community Edition?
- What Are the Differences Between DDS and GaussDB(for Mongo)?
- What Precautions Should Be Taken When Using DDS?
- What Is the Availability of DDS DB Instances?
- Will My DDS DB Instances Be Affected by Other Users' DDS DB Instances?
- Does DDS Support Multi-AZ Deployment?
- Can I Change the VPC for a Created Instance?
- Can I Change the Region for a Created Instance?
- What Is Hidden Node?
- Database Versions
-
Resource and Disk Management
- Which Items Occupy the Storage Space of DDS Instances?
- Which Types of Logs and Files Occupy DDS DB Instance Storage Space?
- Why Is the Storage Space Usage Displayed on the GUI Smaller Than the Actual Usage?
- Why Does Available Disk Space Not Increase After Data Is Deleted?
- Why Is the Resident Memory of a 4 vCPUs/8 GB Memory Replica Set Instance Only 4 GB?
- Capacity Expansion and Specification Changes
-
Database Performance
- When Will a Primary/Standby Switchover Be Triggered for a Cluster or Replica Set?
- High Storage Usage
- What Is the Time Delay for Primary/Secondary Synchronization in a Replica Set?
- How Is Data Transferred Between the Primary and Secondary Nodes of a Replica Set?
- How Do I Clear an Alarm Saying the Shard Memory Usage Exceeds 90%?
- What Can I Do If a Query Error Is Reported After Data Is Written Into the DDS Cluster?
- Database Permissions
-
Creation and Deletion
- How Do I Select Instance Specifications and Nodes?
- Why Is an Instance Not Displayed on the Console After It Is Created?
- Can I Use a Template to Create DDS DB Instances?
- Why Is Data Missing from My Database?
- Will My Backups Be Deleted If I Delete My Cloud Account?
- What Are the Differences Between Instance Deletion and Unsubscription?
-
Database Connection
- What Should I Do If I Fail to Connect to a DDS Instance?
- What Can I Do If the Number of Connections of an Instance Reaches Its Maximum?
- How Do I Query and Limit the Number of Connections?
- What Should I Do If the ECS and DDS Are Deployed in Different VPCs and They Cannot Communicate with Each Other?
- Do Applications Need to Support Automatic Reconnecting to the DDS Database?
- How Do I Create and Log In to an ECS?
- Installing a Client
- Database Usage
- Database Migration
- Database Storage
- Database Parameters
- Backup and Restoration
- Network Security
- Monitoring and Alarm
- Change History (FAQs) Europe Site
-
Product Consulting
-
Troubleshooting
- DDS Instance Node Fault Handling Mechanism
- Connection Failure Message: network error while attempting to run command 'isMaster'
- Connection Failure Messages: No route to host and connection attempt failed
- Connection Failure Message: Authentication failed
- Connection Failure Message: couldn't connect to server
- Connection Failure Message: cannot list multiple servers in URL without 'replicaSet' option
- Connection Failure Message: Timeout while receiving message
- Connection Failure Message: exception: login failed and U_STRINGPREP_PROHIBITED_ERROR
- Change History (Troubleshooting) European Sites
- Videos
Show all
Function Overview
-
OBS 2.0支持
-
Document Database Service (DDS) is an easy-to-use MongoDB-compatible database service that is secure, highly available, reliable, and scalable.It provides DB instance creation, scaling, disaster recovery, backup, restoration, monitoring, and alarm reporting functions with just a few clicks on the DDS console. DDS offers three types of instance architectures to suit different scenarios: cluster, replica set, and single node.
DDS has the following features:
① DDS automatically establishes a three-node replica set architecture. It supports fast deployment, high availability (HA) storage, disaster recovery, and failover.
② DDS provides sharded cluster instances comprising a config node paired with multiple shard and mongos nodes. These cluster instances 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.
All regions
-
-
OBS 2.0支持
-
Each DDS cluster is an independent document database. A sharded cluster consists of a config node, and multiple mongos and shard nodes.
Data read and write requests are forwarded by the mongos nodes, which read configuration settings from config, and then allocate the read and write requests to the shard nodes, making it easy to handle high concurrency scenarios. In addition, each config node, along with the shard nodes in its cluster, are replicated in triplicate to ensure high availability.
① Each mongos is a single node, but you can provision multiple mongos nodes for load balancing and failovers. A single cluster can contain 2 to 32 mongos nodes.
② Each shard is a three-node replica set. A single cluster supports 2 to 32 shard nodes.
③ A config node is a necessary part of a cluster instance, and is also deployed as a replica set. The config node stores instance configuration data.
④ The number of mongos and shard nodes can be increased on the management console. You do not need to use native commands.
⑤ You cannot access data on the config or shard nodes directly. You can only manage the data on the shard nodes though the mongos nodes.
⑥ If the region where the tenant belongs contains three or more AZs, a DB instance can be deployed across these different AZs. In a DB instance, the mongos nodes can be deployed in one or more AZs. The primary, secondary, and hidden config and shard nodes are deployed across three different AZs for disaster recovery.
⑦ Currently, a three-node replica set cannot be directly converted into a cluster.
-
-
OBS 2.0支持
-
A replica set consists of a set of mongod processes. It is a collection of nodes that help ensure data redundancy and reliability.
A replica set consists of three nodes: primary, secondary, and hidden. The three-node architecture is set up automatically, and the three nodes automatically synchronize data with each other to ensure data reliability.
- Primary node: Primary nodes are used to process both read and write requests.
- Secondary node: Secondary nodes are used to process read requests only.
- Hidden node: Hidden nodes are used to back up data.
You can perform operations on the primary and secondary nodes. If a primary node becomes faulty, a secondary node takes over and becomes the primary. If the secondary node is unavailable, a hidden node will take the role of the secondary to ensure high availability.
-
-
OBS 2.0支持
-
A single node instance, as its name suggests, contains only one node and that node can be accessed directly.
As a supplement to the cluster and replica set architectures, the single-node architecture is useful for R&D, testing, and non-core data storage of enterprises. While not as robust as replica sets, single node architecture can be a less expensive way to visualize O&M and provide elastic scaling.
-
-
OBS 2.0支持
-
DDS provides multiple migration schemes to migrate data in different service scenarios:
① Migrating data using DRS.
② Migrating data using mongoexport and mongoimport.
③ Migrating data using mongodump and mongorestore.
DRS is a stable, efficient, easy-to-use cloud service for online database migration.It simplifies data transmission between databases and reduces data transmission costs. You are advised to use DRS to migrate DB instances.
-
-
OBS 2.0支持
-
You can scale up the storage space of a DB instance to suit your service requirements.
-
-
OBS 2.0支持
-
You can change the DB instance class to meet your service requirements.
-
-
OBS 2.0支持
-
DDS allows you to back up databases by configuring an automated backup policy or by creating manual backups. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability.
-
-
OBS 2.0支持
-
You can customize the parameter settings to manage DB engine configurations. DB parameter templates act as a container for engine configuration values that are applied to one or more DB instances.
When creating a DB instance, you can associate a default parameter template or a custom parameter template with the DB instance. After a DB instance is created, you can also change the associated parameter template.
- Default parameter templates
Each default parameter template contains database engine defaults and database system defaults.
- Custom parameter templates
If you need a DB instance with customized parameter settings, you can create a parameter template and change the parameter values as required.
Precautions
- Default parameter templates are unchangeable. When you click their names, you can only view the existing details. If inappropriate settings of a customized parameter template lead to a database startup failure, you can reset the customized parameter template by referring to the settings of the default parameter template.
- 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.
- Improper parameter settings in a parameter template may have unintended adverse effects, including degraded performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter changes to a production DB instance, you should try out these changes on a test DB instance.
- Default parameter templates
-
-
OBS 2.0支持
-
Cloud Eye monitors the status of DDS. 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 instances displayed on the Cloud Eye page is from about 5 to 10 minutes ago, so the data for a newly created DB instance takes about 5 to 10 minutes to show up on Cloud Eye.
All regions
-
-
OBS 2.0支持
-
DDS log management allows you to view database-level error logs, slow query logs, and audit logs, helping you analyze root causes of faults.
-
-
OBS 2.0支持
-
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.
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.