Huawei Cloud Stack 8.5.0 Solution Description 04

DB Instance Description

DB Instance Description

DB Instance Classes

DB instance specifications are listed in the following table. Select appropriate specifications according to your service requirements.

Cluster

For details about specifications of the Community Edition cluster instance, see Table 15-80 and Table 15-81

Table 15-80 config specifications

CPU Type

Specification Type

vCPUs

Memory (GB)

Flavor ID

Default Maximum Number of Connections

x86

General-purpose

2

4

dds.mongodb.s6.large.2.config

1000

Enhanced

2

4

dds.mongodb.c3.large.2.config

Enhanced II

2

4

dds.mongodb.c6.large.2.config

Kunpeng

-

2

4

dds.mongodb.large.arm2.config

Table 15-81 mongos and shard specifications

CPU Type

Specifications

Component

vCPUs

Memory (GB)

Flavor ID

Default Maximum Number of Connections

x86

General-purpose

mongos

2

4

dds.mongodb.s6.large.2.mongos

400

2

8

dds.mongodb.s6.large.4.mongos

400

4

8

dds.mongodb.s6.xlarge.2.mongos

1000

4

16

dds.mongodb.s6.xlarge.4.mongos

1000

8

16

dds.mongodb.s6.2xlarge.2.mongos

4000

8

32

dds.mongodb.s6.2xlarge.4.mongos

4000

16

32

dds.mongodb.s6.4xlarge.2.mongos

8000

16

64

dds.mongodb.s6.4xlarge.4.mongos

8000

shard

2

4

dds.mongodb.s6.large.2.shard

400

2

8

dds.mongodb.s6.large.4.shard

400

4

8

dds.mongodb.s6.xlarge.2.shard

1000

4

16

dds.mongodb.s6.xlarge.4.shard

1000

8

16

dds.mongodb.s6.2xlarge.2.shard

4000

8

32

dds.mongodb.s6.2xlarge.4.shard

4000

16

32

dds.mongodb.s6.4xlarge.2.shard

8000

16

64

dds.mongodb.s6.4xlarge.4.shard

8000

Enhanced

mongos

2

4

dds.mongodb.c3.large.2.mongos

400

2

8

dds.mongodb.c3.large.4.mongos

400

4

8

dds.mongodb.c3.xlarge.2.mongos

1000

4

16

dds.mongodb.c3.xlarge.4.mongos

1000

8

16

dds.mongodb.c3.2xlarge.2.mongos

4000

8

32

dds.mongodb.c3.2xlarge.4.mongos

4000

16

32

dds.mongodb.c3.4xlarge.2.mongos

8000

16

64

dds.mongodb.c3.4xlarge.4.mongos

8000

32

64

dds.mongodb.c3.8xlarge.2.mongos

8000

32

128

dds.mongodb.c3.8xlarge.4.mongos

8000

60

128

dds.mongodb.c3.15xlarge.2.mongos

8000

60

256

dds.mongodb.c3.15xlarge.4.mongos

8000

shard

2

4

dds.mongodb.c3.large.2.shard

400

2

8

dds.mongodb.c3.large.4.shard

400

4

8

dds.mongodb.c3.xlarge.2.shard

1000

4

16

dds.mongodb.c3.xlarge.4.shard

1000

8

16

dds.mongodb.c3.2xlarge.2.shard

4000

8

32

dds.mongodb.c3.2xlarge.4.shard

4000

16

32

dds.mongodb.c3.4xlarge.2.shard

8000

16

64

dds.mongodb.c3.4xlarge.4.shard

8000

32

64

dds.mongodb.c3.8xlarge.2.shard

8000

32

128

dds.mongodb.c3.8xlarge.4.shard

8000

60

128

dds.mongodb.c3.15xlarge.2.shard

8000

60

256

dds.mongodb.c3.15xlarge.4.shard

8000

Enhanced II

mongos

2

4

dds.mongodb.c6.large.2.mongos

400

2

8

dds.mongodb.c6.large.4.mongos

400

4

8

dds.mongodb.c6.xlarge.2.mongos

1000

4

16

dds.mongodb.c6.xlarge.4.mongos

1000

8

16

dds.mongodb.c6.2xlarge.2.mongos

4000

8

32

dds.mongodb.c6.2xlarge.4.mongos

4000

16

32

dds.mongodb.c6.4xlarge.2.mongos

8000

16

64

dds.mongodb.c6.4xlarge.4.mongos

8000

32

64

dds.mongodb.c6.8xlarge.2.mongos

8000

32

128

dds.mongodb.c6.8xlarge.4.mongos

8000

64

128

dds.mongodb.c6.16xlarge.2.mongos

8000

64

256

dds.mongodb.c6.16xlarge.4.mongos

8000

shard

2

4

dds.mongodb.c6.large.2.shard

400

2

8

dds.mongodb.c6.large.4.shard

400

4

8

dds.mongodb.c6.xlarge.2.shard

1000

4

16

dds.mongodb.c6.xlarge.4.shard

1000

8

16

dds.mongodb.c6.2xlarge.2.shard

4000

8

32

dds.mongodb.c6.2xlarge.4.shard

4000

16

32

dds.mongodb.c6.4xlarge.2.shard

8000

16

64

dds.mongodb.c6.4xlarge.4.shard

8000

32

64

dds.mongodb.c6.8xlarge.2.shard

8000

32

128

dds.mongodb.c6.8xlarge.4.shard

8000

64

128

dds.mongodb.c6.16xlarge.2.shard

8000

64

256

dds.mongodb.c6.16xlarge.4.shard

8000

Kunpeng

-

mongos

2

4

dds.mongodb.large.arm2.mongos

400

-

2

8

dds.mongodb.large.arm4.mongos

400

-

4

8

dds.mongodb.xlarge.arm2.mongos

1000

-

4

16

dds.mongodb.xlarge.arm4.mongos

1000

-

8

16

dds.mongodb.2xlarge.arm2.mongos

4000

-

8

32

dds.mongodb.2xlarge.arm4.mongos

4000

-

16

32

dds.mongodb.4xlarge.arm2.mongos

8000

-

16

64

dds.mongodb.4xlarge.arm4.mongos

8000

-

shard

2

4

dds.mongodb.large.arm2.shard

400

-

2

8

dds.mongodb.large.arm4.shard

400

-

4

8

dds.mongodb.xlarge.arm2.shard

1000

-

4

16

dds.mongodb.xlarge.arm4.shard

1000

-

8

16

dds.mongodb.2xlarge.arm2.shard

4000

-

8

32

dds.mongodb.2xlarge.arm4.shard

4000

-

16

32

dds.mongodb.4xlarge.arm2.shard

8000

-

16

64

dds.mongodb.4xlarge.arm4.shard

8000

Replica Set

For details about the replica set instance specifications, see Table 15-82.

Table 15-82 Replica set instance specifications

CPU Type

Specifications

vCPUs

Memory (GB)

Flavor ID

Default Maximum Number of Connections

x86

General-purpose

1

4

dds.mongodb.s6.medium.4.repset

400

2

4

dds.mongodb.s6.large.2.repset

400

2

8

dds.mongodb.s6.large.4.repset

400

4

8

dds.mongodb.s6.xlarge.2.repset

1000

4

16

dds.mongodb.s6.xlarge.4.repset

1000

8

16

dds.mongodb.s6.2xlarge.2.repset

4000

8

32

dds.mongodb.s6.2xlarge.4.repset

4000

16

32

dds.mongodb.s6.4xlarge.2.repset

8000

16

64

dds.mongodb.s6.4xlarge.4.repset

8000

Enhanced

2

4

dds.mongodb.c3.large.2.repset

400

2

8

dds.mongodb.c3.large.4.repset

400

4

8

dds.mongodb.c3.xlarge.2.repset

1000

4

16

dds.mongodb.c3.xlarge.4.repset

1000

8

16

dds.mongodb.c3.2xlarge.2.repset

4000

8

32

dds.mongodb.c3.2xlarge.4.repset

4000

16

32

dds.mongodb.c3.4xlarge.2.repset

8000

16

64

dds.mongodb.c3.4xlarge.4.repset

8000

32

64

dds.mongodb.c3.8xlarge.2.repset

16000

32

128

dds.mongodb.c3.8xlarge.4.repset

16000

60

128

dds.mongodb.c3.15xlarge.2.repset

16000

60

256

dds.mongodb.c3.15xlarge.4.repset

16000

Enhanced II

2

4

dds.mongodb.c6.large.2.repset

400

2

8

dds.mongodb.c6.large.4.repset

400

4

8

dds.mongodb.c6.xlarge.2.repset

1000

4

16

dds.mongodb.c6.xlarge.4.repset

1000

8

16

dds.mongodb.c6.2xlarge.2.repset

4000

8

32

dds.mongodb.c6.2xlarge.4.repset

4000

16

32

dds.mongodb.c6.4xlarge.2.repset

8000

16

64

dds.mongodb.c6.4xlarge.4.repset

8000

32

64

dds.mongodb.c6.8xlarge.2.repset

16000

32

128

dds.mongodb.c6.8xlarge.4.repset

16000

64

128

dds.mongodb.c6.16xlarge.2.repset

16000

64

256

dds.mongodb.c6.16xlarge.4.repset

16000

Kunpeng

-

2

4

dds.mongodb.large.arm2.repset

400

-

2

8

dds.mongodb.large.arm4.repset

400

-

4

8

dds.mongodb.xlarge.arm2.repset

1000

-

4

16

dds.mongodb.xlarge.arm4.repset

1000

-

8

16

dds.mongodb.2xlarge.arm2.repset

4000

-

8

32

dds.mongodb.2xlarge.arm4.repset

4000

-

16

32

dds.mongodb.4xlarge.arm2.repset

8000

-

16

64

dds.mongodb.4xlarge.arm4.repset

8000

Single Node

Table 15-83 lists the specifications of single node instances.

Table 15-83 Single node specifications

CPU Type

Specifications

vCPUs

Memory (GB)

Flavor ID

Default Maximum Number of Connections

x86

General-purpose

2

4

dds.mongodb.s6.large.2.single

400

2

8

dds.mongodb.s6.large.4.single

400

4

8

dds.mongodb.s6.xlarge.2.single

1000

4

16

dds.mongodb.s6.xlarge.4.single

1000

8

16

dds.mongodb.s6.2xlarge.2.single

4000

8

32

dds.mongodb.s6.2xlarge.4.single

4000

16

32

dds.mongodb.s6.4xlarge.2.single

8000

16

64

dds.mongodb.s6.4xlarge.4.single

8000

Enhanced

2

4

dds.mongodb.c3.large.2.single

400

2

8

dds.mongodb.c3.large.4.single

400

4

8

dds.mongodb.c3.xlarge.2.single

1000

4

16

dds.mongodb.c3.xlarge.4.single

1000

8

16

dds.mongodb.c3.2xlarge.2.single

4000

8

32

dds.mongodb.c3.2xlarge.4.single

4000

16

32

dds.mongodb.c3.4xlarge.2.single

8000

16

64

dds.mongodb.c3.4xlarge.4.single

8000

Enhanced II

2

4

dds.mongodb.c6.large.2.single

400

2

8

dds.mongodb.c6.large.4.single

400

4

8

dds.mongodb.c6.xlarge.2.single

1000

4

16

dds.mongodb.c6.xlarge.4.single

1000

8

16

dds.mongodb.c6.2xlarge.2.single

4000

8

32

dds.mongodb.c6.2xlarge.4.single

4000

16

32

dds.mongodb.c6.4xlarge.2.single

8000

16

64

dds.mongodb.c6.4xlarge.4.single

8000

Kunpeng

-

2

4

dds.mongodb.large.arm2.single

400

-

2

8

dds.mongodb.large.arm4.single

400

-

4

8

dds.mongodb.xlarge.arm2.single

1000

-

4

16

dds.mongodb.xlarge.arm4.single

1000

-

8

16

dds.mongodb.2xlarge.arm2.single

4000

-

8

32

dds.mongodb.2xlarge.arm4.single

4000

-

16

32

dds.mongodb.4xlarge.arm2.single

8000

-

16

64

dds.mongodb.4xlarge.arm4.single

8000

DB Engines and Versions

Table 15-84 lists the database version supported by DDS. You need a driver compatible with MongoDB 3.0 or later to access DDS.

Table 15-84 Supported DB engines and versions

Compatibility

CPU Type

Instance Type

Storage Engine

5.0

x86

  • Cluster
  • Replica set

RocksDB

4.4

x86

  • Cluster
  • Replica set
  • Single node

RocksDB

4.2

x86

  • Cluster
  • Replica set
  • Single node

RocksDB

4.0

  • x86
  • Kunpeng
  • Cluster
  • Replica set
  • Single node

WiredTiger

DB Instance Statuses

DB Instance Statuses

Table 15-85 Status and description

Status

Description

Available

A DB instance is running properly.

Abnormal

A DB instance is faulty.

Unhealthy

A node in an available cluster or replica set instance is abnormal or unknown.

Creating

A DB instance is being created.

Creation failed

A DB instance fails to be created.

Backing up

An instance backup is being created.

Restarting

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

Switchover in progress

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.

Adding node

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

Deleting node

The node that failed to be added is being deleted.

Scaling up

The storage space of instance nodes is being expanded.

Enabling audit policy

The instance audit policy is being enabled.

Changing instance class

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

Checking restoration

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

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.

Changing AZ

Data is being migrated from an AZ to another AZ in the same region.

Read Replica

To improve the read capability of the primary node, DDS provides read replicas that can be accessed independently, which is good for handling read-intensive workloads and reducing memory pressure on the primary node. You can also create one or more read replicas to process a large number of read requests and improve throughput.

Differences Between Read Replica and Secondary Node

Node

Description

Application Scenario

Secondary nodes

The secondary node of a replica set instance ensures high availability. If a primary node is faulty, the system automatically switches traffic to the secondary node. If the primary node is faulty, each secondary node may be elected as a new primary node to execute data write requests.

DDS provides an HA connection address to connect to both the primary and secondary nodes and separate read and write operations. In this way, a DDS instance can handle heavy read workloads with ease. In addition, the impact of node faults on services is wakened while the performance is improved.

Read replicas

A read replica in a replica set instance synchronizes data only from the primary node. It does not ensure high availability and will not be elected as the primary node. Read replicas can be connected independently and do not interfere with primary nodes.

Read replicas are useful when applications need to read large amounts of data from existing instances.

Constraints

  • Only replica set instances can have read replicas.
  • Instances that only have read replicas cannot be created.
  • The DDS instance version must be 4.0 or later.
  • Read replicas are used only for processing read requests and do not participate in primary/secondary node election.
  • A maximum of five read replicas can be added to a replica set instance.
  • Data is asynchronously replicated between the primary node and the read replica, and this process will delay by a few seconds.

Functions

  • You can change the number of read replicas to meet fluctuating service demands and reduce service costs.
  • The specifications of a read replica are the same as those of the primary node. Data is automatically synchronized to the read replica.
  • Resources on the primary node are not occupied. Adding or deleting read replicas does not affect services on the primary node.
  • Read replicas can be connected independently and do not interfere with existing primary and secondary nodes.
  • You can monitor the performance of read replicas.
Translation
Favorite
Download
Update Date:2025-08-12
Document ID:EDOC1100404400
Views:60251
Downloads:302
Average rating:0.0Points

Digital Signature File

digtal sigature tool