This topic describes how to create a replica set instance in the ApsaraDB for MongoDB console.

Prerequisites

  • An Alibaba Cloud account is created. For more information, see Sign up with Alibaba Cloud.
  • Your account balance is sufficient if you want to create a pay-as-you-go instance.

Billing

For more information, see Billing items and pricing.

Procedure

After you perform the following operations, ApsaraDB for MongoDB automatically creates your instance. You do not need to manually install or deploy an instance.

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Replica Set Instances.
  4. On the Replica Set Instances page, click Create Instance.
  5. Click Replica Set (Subscription) or Replica Set (Pay-as-you-go).
    Note
    • Subscription: You must pay for an instance when you create the instance. This method is more cost-effective than the pay-as-you-go method. We recommend that you select this method for long-term use. A longer subscription period enables a larger discount.
    • Pay-as-you-go: You are billed on an hourly basis based on the used resources. We recommend that you select this billing method for short-term use. You can reduce costs by releasing your pay-as-you-go instance after you no longer need the instance.
  6. Configure the instance parameters. The following table describes the related parameters.
    Section Parameter Description
    Basic Configuration Region

    The region where the ApsaraDB for MongoDB instance is deployed. After an instance is created, you cannot change the region. Exercise caution when you select the region.

    Instances in the same region (such as an ECS instance and an ApsaraDB for MongoDB instance) can be connected with each other over an internal network.

    Zone

    Select a zone from the region. Zones are geographic locations within a region. Each zone contains independent power supply and network resources. An ECS instance and an ApsaraDB for MongoDB instance in the same zone can be connected over an internal network with minimum network latency. For more information about zones, see Zones.

    Note To implement zone-disaster recovery, you can deploy the replica set instance across multiple zones. For more information, see Create a multi-zone replica set instance.
    Database Version The MongoDB version of the replica set instance. Valid values: 4.2, 4.0, and 3.4.

    For more information about versions, see MongoDB versions and storage engines.

    Note
    Storage Engine

    The storage engine of the instance, which is fixed as WiredTiger.

    Replication Factor The number of nodes in the replica set instance. Select the number of nodes on demand. For example, you can select more nodes for business scenarios with more reads than writes.
    Network Type Classic Cloud services on a classic network are not isolated. Unauthorized access can only be blocked by using security groups or whitelists.
    VPC A virtual private cloud (VPC) is an isolated network with higher security and performance than the classic network.
    Note
    Specifications Plan
    • The CPU and memory occupied by the instance.
    • The maximum number of connections and the maximum input/output operations per second (IOPS) vary based on different specifications. The maximum IOPS is separately measured for read and write operations, and the maximum sum of read and write operations can be twice the maximum IOPS. For more information, see Instance types.
    Storage Space The dedicated storage capacity of each node in the replica set instance.
    Note The storage capacity of a node stores your data, system, and log files.
    Set Password
    • Set Now
    • Set Later

    The password of the root user. You can set a password immediately or during the running of the instance. For more information, see Set a password.

    • The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. Special characters include ! @ # $ % ^ & * ( ) _ + - =
    • The password must be 8 to 32 characters in length.
    Purchase quantity (Available only for subscription instances) Duration You can select one to nine months for the subscription period on a monthly basis, or one to three years for the subscription period on a yearly basis.
    Quantity The number of subscription instances that you want to purchase. You can set an integer in the range of 1 to 20.
    Purchase quantity (Available only for pay-as-you-go instances) Quantity The number of the pay-as-you-go instances that you want to purchase. You can set an integer in the range of 1 to 10.
  7. Click Buy Now.
  8. On the Confirm Order page, read and select ApsaraDB for MongoDB Agreement of Service, and complete the payment.

View the created instance

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Replica Set Instances.

Troubleshoot if you cannot find the instance

Possible cause Solution
You selected a wrong region in the console. Select the region where the instance is deployed. For more information, see View the created instance.
You opened an incorrect page. Select the correct instance list. Perform the following operations:
  1. View the created instance. For more information, see View the created instance.
  2. Select the correct instance list. For more information, see Replica Set Instances.
The instance list in the ApsaraDB for MongoDB console was not updated or was updated before the instance is created. Wait several minutes and then update the instance list to check whether the instance is added to the list.
Resources are insufficient.

The system may fail to create the instance due to insufficient resources. In this case, your payment is refunded. You can check the refund on the Orders page.

After you confirm the refunded fees, you can try one of the following methods:
  • Create an instance in another zone.
  • Submit a ticket. For more information, see Submit a ticket.

What to do next

After you create an instance, perform the following operations:

For more information about instance connection methods and connection scenarios, see Connect to an ApsaraDB for MongoDB instance.