Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ TaurusDB/ User Guide/ Read Replicas/ Adding Read Replicas to a DB Instance

Adding Read Replicas to a DB Instance

Updated on 2025-02-12 GMT+08:00

Scenarios

Read replicas of a DB instance are used to enhance instance capabilities and reduce the read pressure on the primary node. After a DB instance is created, you can add read replicas.

There are synchronous and asynchronous read replicas.

  • Synchronous read replicas: Their failover priority is 1 and specifications are the same as those of the primary node. To avoid failover failures caused by inconsistent specifications between the primary node and read replicas, a DB instance must have a synchronous read replica, and a multi-AZ DB instance must have a synchronous read replica in a different AZ from the primary node.
  • Asynchronous read replicas: Their failover priority is not 1 and specifications are different from those of the primary node.

For more information about read replicas, see Introducing Read Replicas.

Deployment Relationships Between the Primary Node and Read Replicas

  • If you select single-AZ deployment, read replicas are deployed in the same AZ as the primary node.
  • If you select multi-AZ deployment, read replicas are evenly deployed in different AZs to ensure high reliability.

Constraints

  • Each yearly/monthly or pay-per-use DB instance has a maximum of 15 read replicas.
  • Each serverless DB instance has a maximum of 7 read replicas.
  • If all synchronous read replicas are unavailable during a failover, an asynchronous read replica will be promoted to primary.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, locate the instance you want to add read replicas to and choose More > Create Read Replica in the Operation column.

    You can also enter the Create Read Replica page in either of the following ways:

    • Click the instance name to go to the Basic Information page. In the upper right corner of the page, click and choose Create Read Replica.
      Figure 1 Creating read replicas on the Basic Information page
    • Click the instance name to go to the Basic Information page. In the upper right corner of the page, click and choose View Instance Topology. In the instance topology, click Create Read Replica.
      Figure 2 Creating read replicas in the instance topology

  5. On the displayed page, set required parameters.

    Table 1 Parameter description

    Parameter

    Description

    Billing Mode

    • Pay-per-use DB instance: Pay-per-use and serverless read replicas can be added.
    • Yearly/Monthly DB instance: Yearly/Monthly, pay-per-use, and serverless read replicas can be added.
    • Serverless DB instance: Only serverless read replicas can be added.

    Failover Priority

    Failover priority ranges from 1 for the first priority to 16 for the last priority. This priority determines the order in which read replicas are promoted when recovering from a primary node failure. Read replicas with the same priority have a same probability of being promoted to the new primary node. You can configure a failover priority for up to 9 read replicas, and the default priority for the remaining read replicas is -1, indicating these read replicas cannot be promoted to primary. You can change the failover priority of a read replica.

    NOTE:
    • Serverless DB instance: The failover priority for the primary node can only be 1, while that for a newly added read replica can be 1 to 15.
    • Yearly/Monthly DB instance: When a pay-per-use or serverless read replica is added, the failover priority is -1 by default and cannot be changed.
    • Pay-per-use DB instance: When a serverless read replica is added, the failover priority is -1 by default and cannot be changed.

    AZ

    TaurusDB multi-AZ instances allow you to select an AZ when creating a read replica.

    • If no AZs are specified, the created read replicas are evenly distributed in each AZ.
    • If too many nodes are created in a specified AZ, the read replicas may fail to be created due to insufficient resources.
    NOTE:
    • To specify AZs, submit an application by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
    • Serverless DB instances do not allow you to specify AZs for read replicas.

    Instance Specifications

    This parameter is only available for cluster instances.

    If the failover priority is set to 1, the specifications of read replicas must be the same as those of the primary node.

    Quantity

    A DB instance can contain up to 15 read replicas.

  6. For a yearly/monthly instance, click Next and select a payment mode.
  7. For a pay-per-use instance, click Next.
  8. Check the read replica settings.

    • If you need to modify the settings, click Previous.
    • If you do not need to modify the settings, click Submit.

  9. View the new read replicas in the Node List area of the Basic Information page. You can also promote a read replica to primary or delete a read replica.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback