Help Center> Document Database Service> Getting Started> Getting Started with Clusters> Buying a Cluster Instance> Quick Config
Updated on 2024-04-02 GMT+08:00
View PDF

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

Procedure

  1. Go to the Guick Config page.
  2. On the displayed page, select a billing mode and configure information about your DB instance. Then, 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.

    Project

    The project corresponds to the current region and can be changed.

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

    Compatible MongoDB Version
    • 4.4
    • 4.2
    • 4.0
    • 3.4

    CPU Type

    DDS supports x86 and Kunpeng CPU architectures.

    NOTE:

    This parameter is available only for MongoDB 4.0 and 3.4. The default value is Kunpeng.

    • 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 Cluster Instance Specifications.

    dds mongos Node Class

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

    dds mongos Nodes

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

    shard Node Class

    For details about shard CPU and memory, see Cluster Instance Specifications. The shard node stores user data but cannot be accessed directly. You can change the class of an instance after it is created. For details, see Changing the Instance Class.

    shard Storage Space

    The value ranges from 10 GB to 2000 GB and must be a multiple of 10. You can scale up an instance after it is created. For details, see Scaling Up a Cluster Instance.

    NOTE:
    • If the storage space you purchased exceeds 600 GB and the remaining storage space is 18 GB, the instance becomes Read-only.
    • If the storage space you purchased is less than 600 GB and the storage space usage reaches 97%, the instance becomes Read-only.

    In these cases, delete unnecessary resources or expand the capacity.

    shard Nodes

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

    config Node Class

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

    config Storage Space

    Based on the functions and minimum requirements of the config node, the storage space of the config node is set to 20 GB by default. You cannot scale up the storage of the node after it is created.
    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, see 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.

    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 Project Management in Enterprise Management User Guide.

    To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Management page is displayed. For details, see Creating an Enterprise Project in 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.

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

  4. Click Back to Instance List. 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.