Updated on 2022-09-20 GMT+08:00

Quick Config

This section describes how to quickly purchase a cluster instance on the management console. DDS helps you quickly configure and create a cluster within several minutes.

Precautions

Each account can create up to 10 cluster instances.

Prerequisites

  • You have registered a HUAWEI CLOUD account.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, click Buy DB Instance.
  5. On the displayed page, click the Quick Config tab.
  6. Select a billing mode. Specify instance details and click Next.

    Figure 1 Basic configurations
    Table 1 Basic configurations

    Parameter

    Description

    Billing Mode

    Select a billing mode, Yearly/Monthly or Pay-per-use.

    • For yearly/monthly instances
    • For pay-per-use instances
      • You are billed for usage based on how much time the service is in use.

    Region

    The region where the resource is located.

    NOTE:

    Instances deployed in different regions cannot communicate with each other through a private network, and you cannot change the region of an instance once it is purchased. Exercise caution when selecting a region.

    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 internal network connections.

    Instances can be deployed in a single AZ or three AZs.

    NOTE:

    The 3-AZ deployment is not available in all regions. If the 3-AZ option is not displayed on the page for you to buy an instance, try a different region.

    • If your service requires low network latency between instances, you deploy the components of the instance in the same AZ. If you select a single AZ to deploy your instance, anti-affinity deployment is used by default. With an anti-affinity deployment, your primary, secondary, and hidden nodes are deployed on different physical machines for high availability.
    • If you want to deploy an instance across AZs for disaster recovery, select three AZs. In this deployment mode, the mongos, shard, and config nodes are evenly distributed across the three AZs.

    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
    NOTE:

    DDS 4.2 is restricted for commercial use. For details, see the DDS notices. To use this version, contact customer service to apply for the required permissions.

    CPU Type

    DDS supports x86 and Kunpeng CPU architectures.

    • x86

      x86 CPUs use the Complex Instruction Set Computing (CISC) instruction set. Each instruction can be used to execute low-level hardware operations. CISC instructions vary in length, and tend to be complicated and slow compared to Reduced Instruction Set Computing (RISC).

    • Kunpeng

      The Kunpeng CPU architecture uses RISC. The RISC instruction set is smaller and faster than CISC, thanks to the simplified architecture. Kunpeng CPUs also offer a better balance between power and performance than x86.

      Kunpeng CPUs offer a high density, low power option that is more cost effective for heavy workloads.

    Specifications

    With an x86 architecture, you have the following options:

    • General-purpose (s6): S6 instances are suitable for applications that require moderate performance generally but occasional bursts of high performance, such as light-workload web servers, enterprise R&D and testing environments, and low- and medium-performance databases.
    • Enhanced II (c6): C6 instances have multiple technologies optimized to provide stable powerful compute performance. 25 GE intelligent high-speed NICs are used to provide ultra-high bandwidth and throughput, making it an excellent choice for heavy-load scenarios. It is suitable for websites, web applications, general databases, and cache servers that have higher performance requirements for compute and network resources; and medium- and heavy-load enterprise applications.

    For details about the supported instance specifications, see Instance Specifications.

    mongos class

    For details about the mongos CPU and memory, see Instance Specifications. You can change the class of an instance after it is created. For details, see Changing the Instance Class.

    mongos quantity

    The value ranges from 2 to 16. You can add nodes to an instance after it is created if necessary. For details, see Adding Cluster Instance Nodes.

    shard class

    For details about the shard CPU and memory, see Instance Specifications. You can change the class of an instance after it is created. For details, see Changing the Instance Class.

    shard quantity

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

    The value ranges from 2 to 16. You can add nodes to an instance after it is created if necessary. For details, see Adding Cluster Instance Nodes.

    config class

    For details about the CPU and memory of the config node, see Instance Specifications. You can change the class of an instance after it is created. For details, see Changing the Instance Class.

    config storage space

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

    Figure 2 Network, Required Duration, and Quantity
    Table 2 Network settings

    Parameter

    Description

    VPC

    The VPC where your DB instances are located. A VPC isolates networks for different services. It allows you to easily manage and configure private networks and change network configurations. 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 creates one for 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 security reasons.

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

    NOTE:

    IPv6 subnets are not supported. You are advised to create and select IPv4 subnets.

    Security Group

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

    If there are no security groups available, DDS creates one for you by default.

    NOTE:

    Ensure that there is a security group rule configured that allows clients to access instances. For example, select an inbound TCP rule with the default port 8635, and enter a subnet IP address or select a security group that the instance belongs to.

    Enterprise Project

    Only enterprise users can use this function. To use this function, contact customer service.

    An enterprise project is a cloud resource management mode, in which cloud resources and members are centrally managed by project.

    Select an enterprise project from the drop-down list. The default project is default. For more information about enterprise project, see Enterprise Management User Guide.

    Table 3 Required duration and quantity

    Parameter

    Description

    Required Duration

    The length of your subscription if you select Yearly/Monthly billing. Subscription lengths range from one month to three years.

    Auto-renew

    • By default, this option is not selected.
    • If you select this option, the auto-renew cycle is determined by the length of the subscription.

    Quantity

    The purchase quantity depends on the cluster instance quota. If your current quota does not allow you to purchase the required number of instances, you can apply for an increased quota. Yearly/Monthly instances that were purchased in batches have the same specifications except for the instance name and ID.

    Table 4 Default configuration items

    Specifications

    Value

    Editable After Instance Creation

    DB Instance Name

    dds-6c01

    Yes

    CPU Type

    x86

    No

    Storage Engine

    WiredTiger

    No

    Password Settings

    Not configured

    Yes

    SSL

    Disabled

    Yes

    Database Port

    8635

    Yes

    Cluster Parameter Template

    Default-DDS-4.0-Mongos

    Default-DDS-4.0-Shard

    Default-DDS-4.0-Config

    Yes

    Tags

    Not configured

    Yes

    Advanced Settings

    Not configured

    Yes

    • Some settings are configured by default during purchase, but can still be modified after the instance is created. If you do not see a setting listed for your instance, click Custom Config.
    • Instance performance depends on the specifications you select during creation. The hardware configuration items that can be selected include the node class and storage space.

  7. On the displayed page, confirm the instance details.

    • For yearly/monthly instances
      • If you need to modify the specifications, click Previous to return to the previous page.
      • If you do not need to modify the specifications, read and agree to the service agreement and click Pay Now to go to the payment page and complete the payment.
    • For pay-per-use instances
      • If you need to modify the specifications, click Previous to return to the previous page.
      • If you do not need to modify the specifications, read and agree to the service agreement and click Submit to start creating the instance.

  8. After a DDS instance is created, you can view and manage it on the Instances page.

    • When an 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 an instance is created, you can modify or disable the automated backup policy. An automated full backup is immediately triggered after the creation of an instance.
    • Yearly/Monthly instances that were purchased in batches have the same specifications except for the instance name and ID.