Buying and Connecting to a Multi-primary Instance

Billing Mode

Select Pay-per-use.

Region

Region where the instance is deployed

DB Instance Name

The name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

• If you create multiple instances at a time, a hyphen (-) followed by a number with four digits will be appended to the instance name, starting with -0001. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.
• The names for instances created in batches must consist of 4 to 59 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

DB Engine Version

TaurusDB V2.0

Kernel Version

Select 2.0.45.230950. For details about the updates in each minor kernel version, see TaurusDB Kernel Version Release History.

DB Instance Type

Select Multi-primary.

A multi-primary instance can contain 2 to 63 primary nodes, with no read replicas. Such an instance can process multiple reads and writes, delivering excellent read/write performance at high concurrency.

Storage Type

• DL6

  The original Shared storage. The default storage type of TaurusDB instances created before July 2024 is Shared storage, while that of TaurusDB instances created in July 2024 and beyond is DL6.

  DL6-based instances achieve zero RPO with a 3-AZ deployment and deliver better performance and higher peak throughput. They are suitable for core application systems that are sensitive to performance and have demanding requirements on storage I/O during peak hours, such as those in finance, e-commerce, government, and gaming.

• DL5

  A new storage type. With Huawei Cloud's hardware and network infrastructure technologies, DL5-based instances maintain the same high availability as DL6-based instances with 3 AZs and zero RPO.

  Compared with DL6-based instances, although the peak performance of DL5-based instances may decrease, the cost per unit capacity is significantly reduced. DL5-based instances are suitable for CPU-intensive sub-core business systems or application modules that focus on minimal costs.

For more information about storage types, see Storage Types.

AZ Type

An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Some regions support both single-AZ and multi-AZ deployment and some only support single-AZ deployment.

• Single-AZ: All read/write nodes are deployed in the same AZ.
• Multi-AZ: The read/write nodes are evenly deployed in different AZs to ensure high reliability.

Time Zone

You need to select a time zone for your instance based on the region hosting your instance. The time zone is selected during instance creation and cannot be changed after the instance is created.

Instance Specifications

TaurusDB is a cloud-native database that uses the shared storage. To ensure workload stability in high read/write pressure, the system controls the read/write peaks of DB instances based on instance specifications. For details about how to select specifications, see Performance White Paper.

CPU Architecture

Select x86 or Kunpeng.

• x86: x86 instances use Intel® Xeon® Scalable processors and feature robust and stable computing performance. When working on high-performance networks, the instances provide the additional performance and stability that enterprise-class applications demand.
• Kunpeng: Kunpeng instances use Kunpeng 920 processors and 25GE high-speed intelligent NICs for powerful compute and high-performance networks, making them an excellent choice for enterprises needing cost-effective, secure, and reliable cloud services.

Nodes

This parameter is mandatory for multi-primary instances. Each multi-primary instance requires at least two primary nodes. You can create up to 63 primary nodes at a time. All primary nodes are both readable and writable.

You can also add read/write nodes after an instance is created. For details, see Adding Read/Write Nodes to a Multi-primary Instance.

Storage

It contains the system overhead required for inodes, reserved blocks, and database operations.

Storage will be scaled up dynamically based on the amount of data that needs to be stored, and is billed hourly on a pay-per-use basis.

Backup Space

TaurusDB provides free backup space equal to the amount of your used storage. After the free backup space is used up, you will be billed for the additional space on a pay-per-use basis.

VPC

• A dedicated virtual network where your instance is located. It isolates networks for different workloads to enhance security.

  TaurusDB allocates a default VPC (default_vpc) for your instance. You can also use an existing, new, or shared VPC and subnet.

  • To use an existing VPC and subnet, select an existing VPC and subnet under the current account from the drop-down lists.
  • To use a new VPC and subnet, create a VPC and subnet, and then select the VPC and subnet from the drop-down lists.

    For details about how to create a VPC and subnet, see "Creating a VPC and Subnet" in Virtual Private Cloud User Guide.

  • To use a shared VPC and subnet, select a VPC and subnet that another account shares with the current account from the drop-down lists.

    With Resource Access Manager (RAM), you can share subnets in a VPC with one or more accounts, so you can easily configure and manage multiple accounts' resources at low costs.

    For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide.

  NOTICE:

  After a DB instance is created, the VPC cannot be changed.

Security Group

Enhances security by controlling access to TaurusDB from other services. When you select a security group, you must ensure that it allows the client to access instances.

If no security group is available or has been created, TaurusDB allocates a security group to your instance by default.

Database Proxy

You must enable Database Proxy for multi-primary instances. Then you can use proxy addresses to connect to your databases.

Proxy Instance Specifications

You can select the proxy instance specifications as needed.

Proxy Instance Nodes

You can create 2 to 16 proxy instance nodes.

Administrator

The default login name for the database is root.

Administrator Password

It must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?,()&$|.). Enter a strong password and periodically change it to improve security and defend against threats such as brute force cracking attempts.

Keep this password secure. If lost, the system cannot retrieve it.

After an instance is created, you can reset this password. For details, see Resetting the Administrator Password.

Confirm Password

Enter the administrator password again.

Parameter Template

Contains engine configuration values that can be applied to one or more instances.

In the drop-down list, you can view the default parameter template (Default-GaussDB-for-MySQL 8.0), high-performance parameter template (Default-GaussDB-for-MySQL 8.0-High Performance), and all custom parameter templates in the current region. You can select an appropriate parameter template as required.

For more information about parameter templates, see Parameter Template Management. For more information about the high-performance parameter template, see Introducing the High-Performance Parameter Template.

You can modify the instance parameters as required after a DB instance is created. For details, see Modifying Parameters of a DB Instance.

Table Name

Specifies whether table names are case sensitive. This option cannot be changed later.

• Case sensitive: Table names are case sensitive.
• Case insensitive: Table names are case insensitive and are stored in lowercase letters by default.

Enterprise project

Only available for enterprise users. If you want to use this function, contact customer service.

An enterprise project provides a way to manage cloud resources and enterprise members on a project-by-project basis.

You can select an enterprise project from the drop-down list. The default project is default.

Tag

Tags a DB instance. This parameter is optional. Adding tags to DB instances helps you better identify and manage the DB instances. Each DB instance can have up to 20 tags.

<hostIP>

Proxy address.

Click the multi-primary instance name, choose Database Proxy in the navigation pane, and view the proxy address in the proxy instance list.

<port>

Database port. By default, the value is 3306.

Click the multi-primary instance name, choose Database Proxy in the navigation pane, and view the database port in the proxy instance list.

<userName>

The username of the database administrator account. The default username is root.